I ran into the same problem yesterday. It seemed to happen when a service implement method declares that it throws a service-specific exception (e.g., public void process(PO po) throws PoException). A Java2WSDL bug, apparently.
Workaround (simple, but not practical): remove service-specific exceptions
Workaround (practical, but not pretty):
Run Java2WSDL with --style RPC --use ENCODED
Manually modify WSDL to change "style" to document and "use" to literal
Run WSDL2Java --server-side
Compare signatures of your service methods with signatures of generated
service methods. Modify your methods to match if needed.
Deploy with generated deploy.wsddGood luck,
Mike
Stuart Barlow wrote:
I have just come across the bad QName error when trying to create a DOCUMENT/LITERAL service using AXIS and Java2WSDL...
Attempted to write schema for bad QName (no namespace) : fault
Is there a workaround? I could not see a mention of any in the mailing list.
Or will I need to wait for a 1.2 release?
Ta, Stuart.
--
Mike Woinoski Pine Needle Consulting mailto:[EMAIL PROTECTED]
