axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amila Chinthaka Suriarachchi (JIRA)" <>
Subject [jira] Resolved: (AXIS2-2824) parse-method does not work with pure JDK 1.6 (no WoodStox)
Date Tue, 26 Jun 2007 13:59:25 GMT


Amila Chinthaka Suriarachchi resolved AXIS2-2824.

    Resolution: Fixed

resolved the issue with revision 550806. thanks Schork

> parse-method does not work with pure JDK 1.6 (no WoodStox)
> ----------------------------------------------------------
>                 Key: AXIS2-2824
>                 URL:
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: adb
>    Affects Versions: 1.2, 1.1.1
>            Reporter: Andreas Schörk
>            Assignee: Amila Chinthaka Suriarachchi
> I generated ADB-Binding using WSDL2Java. First I included only the necessary Jars in
the eclipse-project so wstx...jar was not there and the JDK 1.6 Implementation of XMLStreamReader
was used to parse.
> So the bug is easily reproduced by just removing wstx...jar and using Java 1.6 runtime.
As soon as adb parses xml with existing Attributes those are null or in Axis2 1.2 an exception
occurs if the attribute is mandatory.
> The generated Code called getAttributeValue("",....) quite often. This always lead to
return null instead of the really existing value.
> The cause for this is that:
>   according to

>   The namespace should be null, if it is not to be checked. 
> So internally the namespace gets checked and null is compared to empty string which leads
to no match.
> There was a discrepancy in the definition of XMLStreamReader of 1.5, namespace should
be null and may not be null. 
> This has been solved in 1.6 now namespace may be null.
> Therefore I think in the future, in case of not wanting to check the namespace, null
should be used as parameter as far as I know 
> Woodstox handled this also right.
> This could easily be solved by a <xsl:choose > in adbbeantemplate.xsl

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message