On Tue, 2010-06-08 at 15:25 +0200, Christian Gosch wrote:
> Are you able to contact other people who might have had success in 
> connecting to this service and using this method, maybe through support 
> personnel or a forum of the service provider?
> 
> What about manually changing the WSDL to make it match what is really 
> happening (and then regenerate the code)? 
> 

Yeah, thank you very much Christian. I patched the wsdl and added the
element and now works like a charm. Meaning their file is simply wrong.

Now the question is why they have an outdated definition and when they
will fix it.

Thanks again that help me a lot in tracking down the problem.

salu2

> Of course this would be ugly, but if a 3rd party service declares <A/> 
> and does <B/> and is not willing to do what it declares, I do not see 
> another chance of hope. (But this is obviously impossible if the 
> mentioned method call returns envelopes different to the returned data 
> of all other method calls: This indeed would be a problem of the service 
> provider :-( )
> 
> If on the other hand the data *do* match the WSDL after exact manual 
> check of the data against the WSDL, and thus the "misunderstanding" 
> seems to be caused by Axis2, then you may try to check the 
> communications setup: I had problems because by default Axis2 uses 
> "chunked" data transfer, but the called 3rd party service did not know 
> anything about chunking. (But this is only an example and does not match 
> your problem really.)
> 
> hth,
> Christian Gosch
> inovex GmbH
> 
> 
> > -----Original Message-----
> > From: Thorsten Scherler [mailto:scher...@gmail.com]
> > Sent: Tuesday, June 08, 2010 2:22 PM
> > To: java-user@axis.apache.org
> > Subject: Returning method returns xml that is not valid
> > 
> > Hi all,
> > 
> > I am integrating a 3rd party webservice over which I have no control. 
> I
> > used wdsl2java to create my client and I can connect to the service
> > fine. However there is one method that returns a soap env that is not
> > valid against the wdsl I created the client against.
> > 
> > I have asked to generate the wdsl again because I had the suspicion 
> that
> > it just not up to date, but they have send me the file unchanged in 
> the
> > interesting aspect. I am not sure how this can happen nor how to fix 
> it.
> > Did somebody had seen similar issues and know a way to fix it? Any
> > feedback is very welcome.
> > 
> > [...]
> > 
> > --
> > Thorsten Scherler <thorsten.at.apache.org>
> > Open Source Java <consulting, training and solutions>
> > 
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
> For additional commands, e-mail: java-user-h...@axis.apache.org
> 

-- 
Thorsten Scherler <thorsten.at.apache.org>
Open Source Java <consulting, training and solutions>


---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
For additional commands, e-mail: java-user-h...@axis.apache.org

Reply via email to