Scott Kurz wrote:
Sebastien, I'm surprised the package names would be different. What is
the namespace you're using that isn't mapping to the same package in each
tool?
Just curious...
My app is an order processing app with the following:
WSDL service namespace:
http://sample/Order/Binding
WSDL Order portType namespace:
http://sample/Order
The CXF tool generates interface sample.order.Order
The JAXWS RI tool generates interface sample.order.binding.Order
I gave the same WSDL file (containing the WSDL service) to both tools.
One could argue that both are correct vs the JAX-WS spec as they
generate a correct package name from the namespace of 'the' WSDL
definition, but the funny thing is that they do not pick the same WSDL
definition... JAXWS-RI picks the input definition given to the tool and
CXF the definition that actually contains the portType... and the JAXWS
spec doesn't seem to state which one should be picked (at least I
couldn't find it).
IMHO the CXF behavior is better, but I've not read all 150 pages of the
JAX-WS spec so I may be missing something :)
--
Jean-Sebastien
