Yep. JAX-WS/JWS spec compliance issue.
It's actually something to be careful of. I ran into a similar issue
yesterday.In one of my codefirst things, I moved the interface out
of the package with the server and all kinds of things broke as the
generated wsdls and schemas had all
I'm not sure, perhaps it was designed that way so the sub-WSDL could be
reusable with other outer WSDLs? Or might only need to be cached once
for multiple outer WSDLs, perhaps.
Glen
Am Mittwoch, den 08.08.2007, 11:53 -0700 schrieb Jason Rosenberg:
Hi,
I just converted a simple app from
Hi Jason,
It was fixed in https://issues.apache.org/jira/browse/CXF-669,
if the SEI and Impl have different targetNamespaces, we do generate two
wsdls
James
I figured it out, it had to do with the 'targetNamespace'
Apparently CXF requires both the interface and implementing classes to
