axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From j...@apache.org
Subject [jira] Commented: (AXIS-1368) Java2WSDL generates elements with the same QName if more than one service-specific fault is present
Date Wed, 26 May 2004 09:26:00 GMT
The following comment has been added to this issue:

     Author: Andrei Iltchenko
    Created: Wed, 26 May 2004 2:25 AM
       Body:
I just discovered that the symptoms I described above are applicable to Axis 1.1 final release.
The situation with the current nightly build is much worse -- it simply fails to create a
second element:


    <schema elementFormDefault="qualified" targetNamespace="http://localhost:8081/services/DomainService">
      <element name="msg" type="tns1:AlturaPostConditionException" /> 
    </schema>
  </wsdl:types>
  <wsdl:message name="AlturaPreConditionException">
    <wsdl:part element="impl:msg" name="msg" /> 
  </wsdl:message>
  <wsdl:message name="AlturaPostConditionException">
    <wsdl:part element="impl:msg" name="msg" /> 
  </wsdl:message>

This is down to the following change in 'Types.writeSchemaElementDecl':

        if (writtenElementQNames.contains(qname)) {
            throw new AxisFault(
                    Constants.FAULT_SERVER_GENERAL,
                    Messages.getMessage(
                            "duplicateSchemaElement", qname.toString()), null, null);
        }

I'll supply a patch shortly.
---------------------------------------------------------------------
View this comment:
  http://issues.apache.org/jira/browse/AXIS-1368?page=comments#action_35722

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/AXIS-1368

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: AXIS-1368
    Summary: Java2WSDL generates elements with the same QName if more than one service-specific
fault is present
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Axis
 Components: 
             WSDL processing
   Versions:
             current (nightly)

   Assignee: 
   Reporter: Andrei Iltchenko

    Created: Tue, 25 May 2004 6:19 AM
    Updated: Wed, 26 May 2004 2:25 AM

Description:
Java2WSDL generates elements with the same QName for document/literal or "wrapped" style web
service components if more than one service-specific fault is present.

This gives rise to ill-formed wsdl documents like the one below (the whole document is attached):

  <wsdl:types>
  <schema targetNamespace="http://businesslogicxsdschema.webservices.integration.sample1">
      <complexType name="AlturaPostConditionException">
        <sequence>
          ...
        </sequence>
      </complexType>
      <complexType name="AlturaPreConditionException">
        <sequence>
          ...
        </sequence>
      </complexType>

    </schema>
    
    <schema targetNamespace="http://cwnl-c1995.nl.compuware.com:8081/services/DomainService">
      <!-- The following two declarations are ill-formed -->
      <element name="msg" type="tns1:AlturaPostConditionException" /> 
      <element name="msg" type="tns1:AlturaPreConditionException" /> 
    </schema>

  </wsdl:types>

  <wsdl:message name="AlturaPostConditionException">
    <wsdl:part element="impl:msg" name="msg" /> 
  </wsdl:message>
  <wsdl:message name="AlturaPreConditionException">
    <wsdl:part element="impl:msg" name="msg" /> 
  </wsdl:message>

The cause of the problem is an omission in the 'Types.writeElementDecl' method, which fails
to keep track of names that have already been used.




---------------------------------------------------------------------
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


Mime
View raw message