[ http://issues.apache.org/jira/browse/AXIS2-594?page=all ]
Venkatakrishnan updated AXIS2-594:
----------------------------------
Attachment: Java2WSDL - Axis2 Patch - 20-Apr .txt
This patch fixes this problem. Now the generated WSDL will create a separate
schema element for each java package. Schema defns. generated for classes
belonging to a package will now be added to the corresponding schema element.
The target namespaces for the schema elements are derived from the name of the
Java package with a suffix "/xsd".
Thus the type definitions within the WSDL will now contain all relevant
information for proper generation of Java code.
> Java2WSDL generates all types under a single schema element and namespace
> even if relevant java classes belonged to differnt Java packages
> ------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AXIS2-594
> URL: http://issues.apache.org/jira/browse/AXIS2-594
> Project: Apache Axis 2.0 (Axis2)
> Type: Bug
> Environment: Codebase as it exists in modules/ java2wsdl as of 20th April
> 2006
> Reporter: Venkatakrishnan
> Attachments: Java2WSDL - Axis2 Patch - 20-Apr .txt
>
> Java2WSDL generates all types under a single schema element and namespace
> even if relevant java classes belonged to differnt Java packages. When the
> generated WSDL is used to generate Java code it will lead to incorrect
> packaging of Java classes. Besides, grouping all types under a single
> namespace could result in type collisions
--
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
