Win a copy of Murach's Python Programming this week in the Jython/Python forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

Axis2 databinding problem  RSS feed

 
Todd Johnson
Ranch Hand
Posts: 61
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I'm using Axis2 to generate a client from WSDL. I'm having a problem with the databinding. The WSDL I'm using is somewhat complex, so to illustrate the problem I created some simpler WSDL. Consider this ficticious service that takes as a request a last name, and then returns as a response the husband (first name, last name) and wife (first name, last name, maiden name) registered with that last name.

Here are how the types are defined in the WSDL:


In Axis2 it doesn't handle this correctly. The FamilyLookupRequest object is created correctly. But because the FamilyLookupResponse has nested complex types Axis2 does not create the FamilyLookupResponse class correctly. Axis2 creates the husband_type0 and wife_type1 classes correctly. However the FamilyLookupResponse contains a husband and wife member, but they are defined as OMElements instead of their correct type (husband_type1, and wife_type0).

If I change the WSDL as shown below, Axis2 will then create the classes correctly. Any ideas? Is this a bug?


Lastly Axis 1.4 handles either version of the WSDL correctly.
[ August 31, 2006: Message edited by: Todd Johnson ]
 
Todd Johnson
Ranch Hand
Posts: 61
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Just an update for anyone else having the problem. This is a bug in Axis 2 release 1.0. ADB should be able to handle those anonymous inner types, but it doesn't. I grabbed the latest development version and it works as it should.
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!