Win a copy of The Way of the Web Tester: A Beginner's Guide to Automating Tests this week in the Testing forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

A problem parsing the response envelope.

Krzysiek Hycnar
Ranch Hand
Posts: 74
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi all,

I've got a weird problem trying to consume a Web Service published by a third party company. The problem occures when the client is trying to parse the response envelope. In case of JAXWS based client instead of a non blank string, null value is returned, and if the JAXRPC client is used I get the following exception:

I managed to fix the problem in the JAXRPC client by manually editing one of the generated classes - I had to replace the originally generated part...


Also, as you can see below in the sample response envelope returned by the service the create_scheduleResponse message is defined as: <create_scheduleResponse xmlns="urn:NetBanxDirectDebit"> and that suggests that the above exception is raised because the parser is expecting the response element not to be placed within the urn:NetBanxDirectDebit namespace (and obviously creating the QName manually with the namespace specified fixed the problem).

The wsdl looks like follows (some parts of it have been cut):

Sample request envelope:

and a sample response envelope:

I believe manual editing of the generated stubs is not the way to go, at the same time I admit, I'm a newbie when it commes to Web Services, so my requestion is:

What can be said having the above data? Is there any specific way I need to generate the client stubs, or the wsdl does not quite describe the service itself?

Thank you in advance for any help!
[ December 08, 2008: Message edited by: Krzysiek Hycnar ]
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic