Validating the wsdl against the ws i basic profile
Basic Profile is organized around base specifications.
Profile adds constraints and guidance as to their interoperable usage based upon implementation experience.
These assumptions are made for the purposes of this chapter because otherwise they would apply very broadly.
For example, if the usage of Soap Extensions were considered for each rule, then a large portion of the rules would be listed as potentially compliant since a custom Soap Extension allows very flexible control of Web service behavior allowing for violation of the rule.
The Call Web Service Smart Service allows you to integrate data from web services within your process and automatically create a custom data type with it.
This allows for more flexible mapping of web service inputs and outputs.
NOTE: RPC/encoded service styles are not supported, and instead you must use RPC/literal or Document/literal encodings.
The levels are: All the rules are included in the same groups (such as messaging) and order as they are listed in the Basic Profile.
Note that only the rule numbers and directives are included.
Hello, a very newbie here, so please don't be too harsh! I would welcome any help - and apologies for the length of the post!
I have found my way through to using Altova XMLSpy to create what it says is a valid WSDL file (including picking up the Types from an external file as I shall need to reuse them).
XMLSpy is happy, but when I try to push the WSDL through the MS WSDL.