Invalid wsdl generated when service method uses arguments or return types from
different java packages
------------------------------------------------------------------------------------------------------
Key: WSAS-720
URL: http://wso2.org/jira/browse/WSAS-720
Project: WSO2 WSAS
Issue Type: Bug
Affects Versions: 2.2
Environment: winxp
Reporter: Matt Voysey
Assigned To: Afkham Azeez
Create a web service class with a web method having a return type of a class
from a different package to the service class and deploy as an aar service
archive. The generated wsdl returned by WSAS includes multiple <schema>
sections in the <wsdl:types>, each having a different namespace (based on the
different java packages used by the web service) but these <schema> sections do
not have the necessary <xs:import namespace="..."/> tags to make their types
visible to each other, so cross references are invalid. WSDL validator tools
report this as an error. Additionally, web service client generation (tried
with eclipse, netbeans, visual studio) fails with this wsdl.
As an attempted workaround, I moved all of the classes used by the webservice
into the same java package. However, the problem still occurs as the wsdl still
contains 2 namespaces - one for the webservice itself (in namespace
http://ws.foo.com for example) and one for the types it uses (in namespace
http://ws.foo.com/xsd), which still contains invalid cross references.
This is a serious problem for us trying to create web services that do more
than just using and returning basic types (int, string etc.).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://wso2.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Wsas-java-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/wsas-java-dev
