Hi, I've two services deployed using Aegis databinding with Jax-ws. One of them uses a custom data type while the other (an Echoservice with public String getEcho(String in)) simply takes a java string. When I query for the wsdl using "?wsdl", the first service wsdl is a good one with (elementFormdefault & attributeFormDefault as qualified)
<xsd:schema attributeFormDefault="qualified" elementFormDefault="qualified" ... but the wsdl for EchoService results in "unqualified" <xsd:schema attributeFormDefault="unqualified" elementFormDefault="unqualified" ... Both services have a targetNameSpace mentioned (if that makes any difference). Also the moment I make swap String with a custom StringT the wsdl shows "qualified". BTW, xfire shows it qualified for the same service! Would be great help if anyone can point how to make it qualified with Aegis for built-in java types; also a pointer in the AegisDataBinding.createSchemas() code would be great! Thanks for all the help, Surender -- View this message in context: http://www.nabble.com/Aegis-wsdl-generation-with-built-in-java-types-tp21516283p21516283.html Sent from the cxf-user mailing list archive at Nabble.com.
