I have written and deployed a web service that returns a fairly complex javabean object (complex meaning lots of aggregate javabeans). I have successfully called the web service method from a standalone client that I wrote by following the user guide example. I would now like to use the WSDL to generate the java client.
My problem is that the WSDL generated uses namespaces that are never declared in the type section of the WSDL document. Here's a snippet: - <complexType name="EBCaseValue"> - <sequence> <element name="accidentCity" nillable="true" type="xsd:string" /> <element name="accidentDate" nillable="true" type="tns3:Date" /> <element name="accidentState" nillable="true" type="xsd:string" /> <element name="addDate" nillable="true" type="tns3:Date" /> <element name="addLoginId" nillable="true" type="xsd:string" /> The problem is the "tns3:Date" type is never declared in the WSDL. When the Wsdl2Java task runs, it fails on these elements. I've seen mention that this is a bug. Can anyone confirm and more importantly have a work around? Thanks, Bill Pfeiffer
