This seems to be a perennial question, and yet I can't see an answer to
it in the form I'm suffering with.
The dynamic wsdl generated by axis often (always?) has an empty default
namespace in the root: This
is true even of the axis default services such as the wsdl generated by
the axis Vers
aised :
org.xml.sax.SAXException: Invalid element in com.namespace1.Attribute1 -
Node1
I managed to isolate what seems to be the problem : When I put a xmlns="" in
the response element , everything
works fine.
But I'd like to find a solution on Axis side, by eliminating those empty
na
cognition.com><[EMAIL PROTECTED]>
cc
03/12/2004 04:56
PMSubject
Thank you for your help Junaid, but I still think that we have found a bug.
You're right, specifying elementFormDefault="qualified" gives me the output
I want. However, I think the SOAP generated when
elementFormDefault="unqualified" (or is unspecified) is wrong. I think that
specifying xmlns=""
PMSubject
Possible bug: empty namespaces for
attributes using doc-lite
I may have found a bug with Axis' treatment of doc-literal encoding in Axis
1.2 alpha. My basic steps were:
1) Create a WSDL file with complexTypes defined using XML Schema
2) Run wsdl2java to generate my WSDD, skeletons, etc.
The classes generated by WSDL2Java that correspond to my complexTypes
thought I'd answer my own question, correct some typos...
xmlToString() should read "ElementToString()"
The problem arose because, in trying to build a more correct webapp, I put
Oracle's XML parser in my WEB-INF/lib directory (it had been in Tomcat's
lib directory before). It was responsible
