[
https://issues.apache.org/jira/browse/AXIS-2758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634070#action_12634070
]
dricks edited comment on AXIS-2758 at 9/24/08 2:13 AM:
------------------------------------------------------------------
We had the exact same problem today, which stresses everyone each time a new
version of the webservices are published on our intranet.
This problem is critical, having to get in touch with every applications
consuming our webservices each time a string property is added to a resulting
object is a real pain, and almost undoable (as Intranet webservices, they are
designed to be used by anyone wanting to...)
was (Author: dricks):
I had the exact same problem today, which stresses everyone each time a new
version of the webservices are published on our intranet.
This problem is critical, having to get in touch with every applications
consuming our webservices each time a string property is added to a resulting
object is a real pain, and almost undoable (as Intranet webservices, they are
designed to be used by anyone wanting to...)
> faultString: org.xml.sax.SAXException: Invalid element foo
> ----------------------------------------------------------
>
> Key: AXIS-2758
> URL: https://issues.apache.org/jira/browse/AXIS-2758
> Project: Axis
> Issue Type: Bug
> Components: Serialization/Deserialization
> Affects Versions: 1.4
> Reporter: Dominique Jean-Prost
>
> Axis generated stub does not handle correctly changes in wsdl if fields are
> added in a "method" result. I think it could handle it transparently.
> Maybe you could add an option in wsdl2java letting us to choose if we want to
> be strict or not.
> In my example, typeIban was added in wsdl after stub generation.
> AxisFault
> faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
> faultSubcode:
> faultString: org.xml.sax.SAXException: Invalid element in
> com.dexia.sofaxis.test.RibWSDTO - typeIban
> faultActor:
> faultNode:
> faultDetail:
> {http://xml.apache.org/axis/}stackTrace:org.xml.sax.SAXException:
> Invalid element in com.dexia.sofaxis.test.RibWSDTO - typeIban
> at
> org.apache.axis.encoding.ser.BeanDeserializer.onStartChild(BeanDeserializer.java:258)
> at
> org.apache.axis.encoding.DeserializationContext.startElement(DeserializationContext.java:1035)
> at
> org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.java:165)
> at
> org.apache.axis.message.MessageElement.publishToHandler(MessageElement.java:1141)
> at org.apache.axis.message.RPCElement.deserialize(RPCElement.java:236)
> at org.apache.axis.message.RPCElement.getParams(RPCElement.java:384)
> at org.apache.axis.client.Call.invoke(Call.java:2467)
> at org.apache.axis.client.Call.invoke(Call.java:2366)
> at org.apache.axis.client.Call.invoke(Call.java:1812)
> at
> com.dexia.sofaxis.test.ReferentielIbanBindingStub.rechercheRibsByIdsTiers(ReferentielIbanBindingStub.java:224)
> at
> com.dexia.sofaxis.clientws.TestReferentielIban.main(TestReferentielIban.java:32)
> {http://xml.apache.org/axis/}hostname:PODJP
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
