[
https://issues.apache.org/jira/browse/AXIS2-3037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris B updated AXIS2-3037:
---------------------------
Description:
I have an client app that was created and had been working, it makes a call to
one webservice.
The webservice was upgraded, it added some new methods and it also added a new
property (Type) to one of the return types I was using.
Now my app will no longer work, i get a runtime error,
java.lang.RuntimeException: Unexpected subelement Type, when the results are
returned to my service.
If i rebuilt the client stub code using wsdl2java with the new wsdl my app will
work again.
As I understand it, adding fields to a object should not break any existing
code. Any Xml elements returned that are not known elements should be ignored
and not cause exceptions in the client code.
I have tested my assumption with Visual Studio 2005, if i genereate web service
client code using the old wsdl I can still call the new service without an
exception being thrown because of the new Xml element being returned.
Is there some option that I don't know of that will allow for new elements to
be returned without exceptions being throw?
was:
I have an client app that was created and had been working, it makes a call to
one webservice.
The webservice was upgraded, it added some new methods and it also added a new
property (Type) to one of the return types I was using.
Now my app will no longer work, i get a runtime error,
java.lang.RuntimeException: Unexpected subelement Type, when the results are
returned to my service.
If i rebuilt the client stub code using wsdl2java with the new wsdl my app will
work again.
As I understand it, adding fields to a object should not break any existing
code. Any Xml elements returned that are not known elements should be ignored
and not cause exceptions in the client code.
I have tested my assumption with Visual Studio 2005, if i genereate web service
client code using the old wsdl I can still call the old service without an
exception being throws because of the new Xml element being returned.
Is there some option that I don't know of that will allow for new elements to
be returned without exceptions being throw?
> 'RuntimeException: Unexpected subelement' when wsdl adds a new property
> -----------------------------------------------------------------------
>
> Key: AXIS2-3037
> URL: https://issues.apache.org/jira/browse/AXIS2-3037
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: codegen
> Affects Versions: 1.2
> Environment: Win2k3, Java 6.0, Axis2 1.2
> Reporter: Chris B
> Priority: Critical
> Attachments: futures_new.wsdl, futures_old.wsdl, TestRunner.java
>
>
> I have an client app that was created and had been working, it makes a call
> to one webservice.
> The webservice was upgraded, it added some new methods and it also added a
> new property (Type) to one of the return types I was using.
> Now my app will no longer work, i get a runtime error,
> java.lang.RuntimeException: Unexpected subelement Type, when the results are
> returned to my service.
> If i rebuilt the client stub code using wsdl2java with the new wsdl my app
> will work again.
> As I understand it, adding fields to a object should not break any existing
> code. Any Xml elements returned that are not known elements should be ignored
> and not cause exceptions in the client code.
> I have tested my assumption with Visual Studio 2005, if i genereate web
> service client code using the old wsdl I can still call the new service
> without an exception being thrown because of the new Xml element being
> returned.
> Is there some option that I don't know of that will allow for new elements to
> be returned without exceptions being throw?
--
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]
