The UDDI V3 WSDL separates out the portType and binding into different WSDL
files with different namespaces. There are no WSDL service definitions for
UDDI published by OASIS, so I have invented some, each in a different
document with a unique namespace.
For example, considering the UDDI inquiry API, I have the following
namespaces:
portType - urn:uddi-org:api_v3_portType
binding - urn:uddi-org:api_v3_binding
service - urn:uddi-org:inquire_v3_service
When I run wscompile I supply the packageName of
org.uddi.v3.wsdl.service.inquire as part of the wsdl element in the
config.xml file and I also supply a namespaceMappingRegistry which maps each
of the other namespaces to unique packages.
However, when the code is generated, all of the WSDL-related code is
generated in the package specified in the packageName attribute, the fact
that the other WSDL entities are imported from other namespaces that have
specific mappings in the namespaceMappingRegistry appears to be ignored.
Is this the intended behavior? I had hoped to allow for the portTypes and
bindings to be mapped to "standard" packages while allowing the code
generated directly from the wsdl:service to be in any package, but it seems
that the only way to get any portable code is to mandate the service
structure and the package that must be used for the service.
John Colgrave
IBM
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_jax-rpc.dev.java.net
For additional commands, e-mail: users-help_at_jax-rpc.dev.java.net