DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7744>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7744 WSDL2Java does not work properly if xsd:import is used Summary: WSDL2Java does not work properly if xsd:import is used Product: Axis Version: beta-1 Platform: Sun OS/Version: Solaris Status: NEW Severity: Critical Priority: Other Component: Basic Architecture AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Schema inclusion (as opposed to wsdl inclusion) results in undefined types, e.g. <xsd:import namespace="http://my.namespace/foo"; location="http://my.wwwserver/foo.xsd";> fails to define WSDL types for types defined in the imported schema. Since WSDL2Java uses the XMLUtils DOM reader which does not enable Xerces schema validation, the Xerces parser does not interpret this directive. If WSDL2Java is changed to enable this feature, the schema is read correctly but the corresponding datatypes are not defined. If the same schema is <wsdl:include> then the types are defined correctly. The same problem occurs for xsi:schemaLocation directives. If this behaviour is intentional, the reasoning should be documented as it is not intuitative
