• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Wrong element appearing in soap message

 
Ranch Hand
Posts: 43
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I have below wsdl generated using AXIS 1.2 Final :






Now when I deploy the service using AXIS 1.2 Final and generate the
response I am getting below soap response from AXIS






instead of









The element name should be <item> instead of <getRRList> inside <getRRList>.
Can anyone please suggest the reason for this. How actually response
element names are created by AXIS ? Can we control the elements name
while generating soap message using AXIS? Thanks in advance for your
time and reply.
 
Bartender
Posts: 2968
6
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
For one stop using overloaded names � it confuses some of the Axis tools (it shouldn't but that's a different matter). For instance:

name="getEROCResponse is also in the "intf" namespace. Use something like this instead:

Get rid of any kind of name overloading in the WSDL and see if the problem still occurs.

See Axis 1.2 or 1.3 Putting Service Params in SOAP Header Section
 
Akram Chotu
Ranch Hand
Posts: 43
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Peer-

Thank you for the response. The wsdl has been generated by AXIS 1.2.1 and I have not handcrafted the wsdl after axis generated. Still any thoughts?
 
Peer Reynders
Bartender
Posts: 2968
6
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Fix the WSDL - use WSDL2Java and see if the problem goes away.
 
Ranch Hand
Posts: 2108
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Akram

After you deploy, you can view the wsdl on the server. Is it the same as the wsdl you pasted above? (I am assuming, based on what you said above, that you generated the wsdl you pasted above, before you deployed.)
 
Akram Chotu
Ranch Hand
Posts: 43
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Jesus-

The wsdl generated dynamically by AXIS and the wsdl generated using JAVA2WSDL are same. My solution seems to be bug in AXIS.
 
eat bricks! HA! And here's another one! And a tiny ad!
a bit of art, as a gift, the permaculture playing cards
https://gardener-gift.com
reply
    Bookmark Topic Watch Topic
  • New Topic