[ http://issues.apache.org/jira/browse/AXIS-2105?page=all ]

Aaron Hamid updated AXIS-2105:
------------------------------

    Attachment: elementdecl.patch

Here is a patch that includes a JUnit test and code to make the test succeed - 
basically assign the name field of SymTabEntry with a naive parsing of the 
qname localpart.

> Regression in ElementDecl/SymTabEntry getName()
> -----------------------------------------------
>
>          Key: AXIS-2105
>          URL: http://issues.apache.org/jira/browse/AXIS-2105
>      Project: Apache Axis
>         Type: Bug
>   Components: Serialization/Deserialization, WSDL processing
>     Versions: 1.2.1
>     Reporter: Aaron Hamid
>     Assignee: Davanum Srinivas
>  Attachments: elementdecl.patch
>
> Using the following schema type as an example:
> <xsd:complexType name="__MyType_in">
>   <xsd:sequence>
>     <xsd:element name="id" nillable="true" type="xsd:string" minOccurs="0"/>
>     <xsd:element name="check_all" nillable="true" type="xsd:boolean" 
> minOccurs="0"/>
>   </xsd:sequence>
> </xsd:complexType>
> In Axis 1.1 ElementDecl.getName() returned the unqualified field name of the 
> element, e.g.:
> getName() on the ElementDecl of "check_all" would return: "check_all"
> In 1.2.1 this seems to have broken.  In Revision 1.10 of ElementDecl, 
> ElementDecl is made to subclass ContainedEntry, and therefore SymTabEntry, 
> and the setName/getName methods that operated on QName were removed and 
> implicitly replaced with the super class SymTabEntry setName/getName that 
> operate on String.  However, the name field of SymTabEntry superclass is 
> never set, so getName on an ElementDecl always returns null.
> e.g.:
> log.debug(ed.getName());
> log.debug(ed.getQName());
> log.debug(ed.getQName().getLocalPart());
> [DEBUG] DynamicType - null
> [DEBUG] DynamicType - __MyType_in>check_all
> [DEBUG] DynamicType - __MyType_in>check_all
> [DEBUG] DynamicType - __MyType_in>check_all
> As you can see, getName() returns null.  My expectation is that it return 
> "check_all".  Currently I am obtaining the QName, and then parsing the 
> substring that starts with '>' to obtain the field name.  I am not familiar 
> with this notation however.  Is it ad-hoc or specified somewhere?

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

Reply via email to