You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@cxf.apache.org by Mayank Mishra <ma...@pramati.com> on 2008/01/17 15:58:34 UTC

Regarding elementFormDefault

Hi,

I am using CXF 2.0.2. I am facing the same issues discussed in the 
following thread,
http://www.nabble.com/Created:-(CXF-1226)-Missing-input-output-param-namespace-in-SOAP-td13870857.html

Using java first approach, with Service class or Interface, generated 
WSDL has,
*elementFormDefault*="unqualified"

Finally wsdl2java generates package-info.java having XmlSchema element 
having NO elementFormDefault attribute (considered as unqualified as 
default option (I understand TCK requires it to be unqualified))

Is hardcoding in package-info.java on server and client is the only 
option? or can I generate package-info.java with this elementFormDefault 
attribute using some switches in wsdltojava or JAXB/JAXWS changes?

Also, Please let me know, is there any patch available on CXF 2.0.2 
which can help to solve this problem, or any solution to CXF-1226 [1] 
which solves this problem.

Do let me know if I made wrong assumptions in approach.

[1]. https://issues.apache.org/jira/browse/CXF-1226

With Regards,
Mayank