axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "AbdelRahman Sinno (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AXIS2-4859) Optional "Ignore Unexpected Elements" mode - allows for forward-compatible clients
Date Fri, 11 Dec 2015 09:45:11 GMT

    [ https://issues.apache.org/jira/browse/AXIS2-4859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15052532#comment-15052532
] 

AbdelRahman Sinno commented on AXIS2-4859:
------------------------------------------

This is a very crucial fix we need it, and we are not yet confident to use 1.7 SNAPSHOT.
So, please someone answer the above question: if I use version 1.7 of axis2-adb-codegen and
axis2-codegen jar (including this fix), does it work with the latest AXIS2 (1.6.3).

Or, what else do you suggest to be able to ignore unexpected elements for NOW ?
Since Apache CXF as not an option due to limitations it has with connection limits being common
to the entire JVM.

> 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.5.2, 1.5.3, 1.6.0
>            Reporter: Dean Holdren
>            Assignee: Ping Liu
>             Fix For: 1.7.0
>
>         Attachments: iu.patch, iu_1_5.patch, iu_trunk.patch, names_v1.response, names_v1.wsdl,
names_v1_client.zip, names_v1_client_with_xsl_change.zip, names_v1_service.zip, names_v2.response,
names_v2.wsdl, names_v2_client.zip, names_v2_service.zip
>
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)

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