axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcel Tilly (JIRA)" <>
Subject [jira] Created: (AXIS-2300) This bug AXIS-1935 seemed not to be fixed
Date Sun, 13 Nov 2005 20:52:21 GMT
This bug  AXIS-1935 seemed not to  be fixed

         Key: AXIS-2300
     Project: Apache Axis
        Type: Bug
  Components: Basic Architecture  
    Versions: 1.2    
    Reporter: Marcel Tilly

The namespace in an item element of an array is xlns:="" but it should be empty:

                  <item xmlns="">

The schema for this problem looks like:

   <complexType name="Position">
     <element name="artikelNr" nillable="true" type="xsd:string"/>
     <element name="menge" type="xsd:int"/>

   <complexType name="ArrayOfPosition" >
     <element maxOccurs="unbounded" minOccurs="0" ref="impl:item"/>
   <complexType name="Positionen">
     <element name="position" nillable="true" type="impl:ArrayOfPosition"/>

Tim from bug axis-1935 has suggested the following bug fix for SerializationContext:

                // -----------------
                // NOTE: I have seen doc/lit tests that use
                // the type name as the element name in multi-ref cases
                // (for example <soapenc:Array ... >)
                // In such cases the xsi:type is not passed along.
                // -----------------
                // The multiref QName is our own fake name.
                // It may be beneficial to set the name to the
                // type name, but I didn't see any improvements
                // in the interop tests.
                //if (name.equals(multirefQName) && type != null)
                //    name = type;
                if (elemQName.getNamespaceURI().equals("")){
                  elemQName = new QName(this.nsStack.getNamespaceURI(""),elemQName.getLocalPart());
                ser.serialize(elemQName, attributes, value, this);

This bugfix works in this case.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message