The service to be invoked by the default soap processor is identified by one of the following ways:
- The combination of the name of the root element of the soap body plus the namespace name of the soap body must map to an existing fully qualified servicename. For example a root node that looks like this:
would attempt to invoke the “addressService:validateAddress” flow service.
- The combination of the the name of the root element of the soap body plus the namespace name of the soap body must map to an entry in the serivce registry that was created using the Universal Name portion of the “Settings” tab for the service you want to invoke. For example a root node that looks like this:
would attempt to find an entry in the universal name service registry for “myNameSpace:myLocalName”. If it succeeded it would invoke the service registered under that universal name (in our case validateAddress).
You can use the pub.universalName:list service to return a list of the entries in the universal name service registry if you are curious about its contents.
The second approach is useful if you want to use documents in your soap request messages that have different root names than your actual service name or if you want to invoke a service several folders deep, but don’t want to expose that structure to external users.
HTH,
Mark Carlson
Conneva, Inc.
#Flow-and-Java-services#Integration-Server-and-ESB#webMethods