Hi Bernhard,

Unexpected subelement Exception is thrown whenever the client/or server
receives an unexpected element in the SOAP message. This can be due to
various issues. Rampart-29 bug is only a small sub-set of many
situations that it can occur. So if you are not using Security, MTOM and
a code generated client at once this may occur. 

Your situation is another sub-set, since you are not using security or
MTOM. If can send the WSDL then Axis2 team will look at it.  

Regards,
Dimuthu




On Wed, 2007-05-16 at 10:26 +0200, Bernhard Breinbauer wrote:
> Hi!
> 
> I'm having a similar problem as described in the thread: working in .NET, 
> but "Unexpected subelement return" when I try to run as axis2 client
> 
> My scenario:
> I have to use a webservice on a proprietary embedded device, therefore i 
> can't 
> change it. Unfortunately the response messages are not composed as described 
> in the wsdl file. One response type in the wsdl has a base type which 
> contains index and name values. The problem ist that the webservice appends 
> them to the end of of the response message instead of to the front. Therefore 
> the sequence of values gets mixed up.
> My axis2 client bails out when parsing this response message with 
> an "Unexpected subelement" error. 
> 
> I know it is not axis2's fault, but is there a possibility to work around 
> this 
> bug? As mentioned above it is not possible to change the webservice 
> implementation and I don't fancy the option to change the wsdl very much.
> 
> So does someone has an tip, advice,...?
> 
> best regards,
> bernhard
> 
> 
> PS: I almost forgot: This bug is related to the above mentioned thread 
> because 
> a .Net based client is working. Apparently the .net implementation is more 
> tolerant in this case. (May be a bug in .net :-)
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to