Hi; Thanks for the reply. But the order is changeable also. But today contract-first approach is hard to obey.So by the time the response changes. So will it make sense if I change my binding? Which binding methodology can easily work when the order of the elements change.?
Yours Ibrahim DEMIR CyberSoft Yazilim Muh. http://www.ibrahimdemir.org ________________________________ From: don t <[email protected]> To: [email protected] Sent: Friday, January 9, 2009 10:18:57 PM Subject: Re: How to get rid of Unexpected SubElement Exception Hi, to make an element optional you can set minOccurs="0" in the WSDL. However elements in the SOAP body must appear in the same order specified in the WSDL. ibrahim demir wrote: > > Hi All; > > I have already said about my problem but want to repeat. I am using Axis2 > and Axis2 Code Generator for Eclipse to generate my client codes. > (Choosing ABD binding) > > As you know when the response has extre elements or the order is different > than the wsdl than it causes and Unexpected Subelemenet exception. Is > there a way to void it. Is it possible to make Axis2 just use the coming > elemenst that are necceassary for it. Or should I change my binding > methodology? > This a very problem for me because the server is not stable about the > responses and is dynamic for being able to response for diffrent requests. > > yours. > > Ibrahim DEMIR > CyberSoft Yazilim Muh. > http://www.ibrahimdemir.org > > > > -- View this message in context: http://www.nabble.com/How-to-get-rid-of-Unexpected-SubElement-Exception-tp21326520p21379854.html Sent from the Axis - User mailing list archive at Nabble.com.
