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

Chuck Williams updated AXIS2-523:
---------------------------------

    Attachment: codegen.patch

This replaces the prior version of codegen.patch to fix the additional issue 
noted in AXIS2-603.

Sorry I was not able to verify all of this in the 1.0 RC1 due to other urgent 
issues.  I am anxiously awaiting 1.0 RC2 and plan to verify everything there.


> Patches to fix and/or work around issues Axis2-518, Axis2-519, Axis2-520, 
> Axis2-521 and Axis2-522
> -------------------------------------------------------------------------------------------------
>
>          Key: AXIS2-523
>          URL: http://issues.apache.org/jira/browse/AXIS2-523
>      Project: Apache Axis 2.0 (Axis2)
>         Type: Bug

>   Components: om, wsdl, databinding
>     Versions: 0.95
>  Environment: All
>     Reporter: Chuck Williams
>     Assignee: Ajith Harshana Ranabahu
>  Attachments: adb.patch, codegen.patch, codegen.patch
>
> The attached patch files fix or work around issues 518 (improper setting of 
> choice variable in ADBBeanTemplate causes all generated adb beans to behave 
> as if they were choices), 519 (add support for recursive data types), 520 
> (serialize 0-length arrays properly in pull parser), 521 (work around 
> OMStaXWrapper failure to honor contract of getElementText), and 522 (add 
> support for choice particles).
> codegen.patch applies to modules/codegen/src and adb.patch applies to 
> module/adb/src, both for the 0.95 distribution source tree.
> All of the issues are fixed by the patches, with these exceptions:
>   1.  Issue 521 is worked around instead of fixed as the errant code has 
> moved to commons.
>   2.  The changes the adb bean parse method (in ADBBeanTemplate) do not use 
> the new state machine mechanism, and so might fail in some cases where that 
> mechanism is important.
> All axis2 tests pass, and I've verified all of this work for an application 
> with a complex wsdl that uses all of these features.

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