[ http://issues.apache.org/jira/browse/AXIS2-365?page=comments#action_12362208 ]
Sanjiva Weerawarana commented on AXIS2-365: ------------------------------------------- Sorry, I was referring to the email discussion we're having about keeping target namespaces ... so the solution for this also appears to be to not lose the WSDL when generating a skeleton. Sanjiva. > Java2WSDL - Problems with schema generated using "?wsdl" > -------------------------------------------------------- > > Key: AXIS2-365 > URL: http://issues.apache.org/jira/browse/AXIS2-365 > Project: Apache Axis 2.0 (Axis2) > Type: Bug > Reporter: Davanum Srinivas > Priority: Blocker > > Generate the service for the wsdl in AXIS2-184 and Look at the schema for > "?wsdl", it is using: > targetNamespace="http://org.apache.axis2/xsd"; > Original WSDL has the namespace: > http://data.soap.highlinedata.com/Data.xsd1 > So basically any client generated from the "?wsdl" *WILL* fail. > Steps: > - Run "w2j" against the wsdl in AXIS2-184 > I used the following: > java org.apache.axis2.wsdl.WSDL2Java -d xmlbeans -o work2 -s -t -ss -sd -uri > http://issues.apache.org/jira/secure/attachment/12321416/DLDataService.wsdl > - CD to work2 directory and run "ant start.server" > - Point your browser to "http://localhost:8080/axis2/services/ > - Click on the link for the service > thanks, > dims -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
