axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dean Holdren (JIRA)" <j...@apache.org>
Subject [jira] Updated: (AXIS2-4859) Optional "Ignore Unexpected Elements" mode - allows for forward-compatible clients
Date Wed, 20 Oct 2010 18:42:25 GMT

     [ https://issues.apache.org/jira/browse/AXIS2-4859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Dean Holdren updated AXIS2-4859:
--------------------------------

    Attachment: iu_trunk.patch
                iu_1_5.patch

Patches for the trunk and 1_5 branch to support "Ignore Unexpected" parameter (-Eiu) for wsdl2java

> Optional "Ignore Unexpected Elements" mode - allows for forward-compatible clients
> ----------------------------------------------------------------------------------
>
>                 Key: AXIS2-4859
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4859
>             Project: Axis2
>          Issue Type: New Feature
>          Components: codegen
>    Affects Versions: 1.6, 1.5.3, 1.5.2
>            Reporter: Dean Holdren
>         Attachments: iu_1_5.patch, iu_trunk.patch
>
>
> Problem: Service provider adds an optional element to the responses it sends, assuming
client can handle, while client is unaware and has not (or cannot) retrieve updated WSDL and
regenerate client.  Axis2 client generated with ADB, cannot handle and throws an exception.
> Solution:
> Optional "Ignore Unexpected Elements" mode for wsdl2java using adb - allows for forward-compatible
clients that can recover from unxpected elements in service responses.
> Based on the work in Issue 3037 - This patch is more up to date, is for both trunk and
1_5 branch, handles more scenarios, and will correctly parse the portion of the response after
the unexpected element.
> To use, pass the "-Eiu" parameter to wsdl2java
> Handles the following scenarios:
> 1) unexpected element in a xsd:choice, xsd:any, xsd:all
> 2) appended unexpected element in a xsd:sequence.
> For xsd:sequence, the unexpected element, and subsequent elements within that sequence
are not captured. If a service adds a new element within a sequence, it should be *appended*,
as the generated client is strict with ordering, and can't differentiate an out-of-order sequence
from an additional inserted element.

-- 
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org


Mime
View raw message