You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by ji...@apache.org on 2004/06/03 15:21:54 UTC
[jira] Commented: (AXIS-526) WSDL generated by Axis does not properly generate references to schemas
The following comment has been added to this issue:
Author: Davanum Srinivas
Created: Thu, 3 Jun 2004 6:20 AM
Body:
Patch is at http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14818
---------------------------------------------------------------------
View this comment:
http://issues.apache.org/jira/browse/AXIS-526?page=comments#action_35884
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/AXIS-526
Here is an overview of the issue:
---------------------------------------------------------------------
Key: AXIS-526
Summary: WSDL generated by Axis does not properly generate references to schemas
Type: Bug
Status: Open
Project: Axis
Components:
WSDL processing
Versions:
1.0
Assignee: Davanum Srinivas
Reporter: Twan van Enckevort
Created: Mon, 25 Nov 2002 12:38 PM
Updated: Thu, 3 Jun 2004 6:20 AM
Environment: Operating System: Windows NT/2K
Platform: PC
Description:
The document http://wavendon.dsdata.co.uk/axis/services/CarRentalQuotes?wsdl
which is generated by Axis does not follow XSD specifications. Furthermore Axis
WSDL2Java will quite happily import this generated document although it does
not meet XSD specifications. So:
1) Axis generates incorrect WSDL
2) Axis WSDL2Java quite happily accepts this incorrect WSDL
The problem with this document is that it contains two schemas where the second
schema references the first schema without properly importing it.
The WSDL 1.1 specifications states that it follows XSD specifications
In the XSD specification section 4.2.3 http://www.w3.org/TR/2001/REC-xmlschema-
1-20010502/#composition-schemaImport in the first sentence after the table it
is stated that a schema from a different namespace should always be imported in
order to reference to it.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira