Operation names for WSDL interfaces include the target namespace in their name (e.g. {some:namespace:uri}
someOperation). This is cumbersome and counterintutive from a user's perspective when selecting operations (e.g. to switchyard://ServiceName?operationName=someOperation). The engine should allow users to omit the namespace in the syntax for their operation selectors. Likewise, all places in the tooling should display only the local name for the operation.
There are a few ways to address this issue:
-
Do not include the target namespace in the operation name when creating the service operations.
-
Allow operations to be resolved using only the local part.
In either case, the engine will need to accommodate existing applications which may be using the namespace.
My preference is the first option. The engine can check the name, and if a match is not found, it can parse the name as a QName, extracting the local part to try again. This would make the ServiceInterface objects created for WSDL interfaces behave similarly to other interface types (i.e. no namespaces).
The tooling will need to be changed as well.
|