• 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

Problem with Namespace Prefixes with Axis1 but not Axis2

 
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Greetings,

I have done Web Service client and server programming for a bit, and have always used Axis2 as my tool of choice. Unfortunately I've run into a situation at work where my code is going to be deployed on a box running a 1.4 JRE , so I am unable to use Axis2 for my current project. I have built a working consumer for the web service I need to interface with in Axis2. When I run it, it creates the following SOAP Request (captured by TCPTrace):



Once I found out that I was unable to use Axis2 in my deployment environment, I downloaded an old version of Axis1, ran its wsdl2java tool, and changed my client around to use the new stubs. My captured Request XML now looks like:




This is causing the service to throw a SOAP Fault because the XXX_IDENTIFIER, PART_NUMBER, and PART_REVISION fields are not assigned to the correct namespace, and the message is viewed as missing required parameters by the service side validator. I looked through the stubs and the fields seem to be Named and Typed correctly in the static TypeDesc initialization block that backs the Serializer (From XXX_IDENTIFIER.java):



Does anyone with Axis1 experience know what I need to change to genereate prefixes or namespace attributes for all of the internal request elements? I'm really kind of stuck on this issue.

Thanks and Regards,

Mike
 
I can't take it! You are too smart for me! Here is the tiny ad:
a bit of art, as a gift, that will fit in a stocking
https://gardener-gift.com
reply
    Bookmark Topic Watch Topic
  • New Topic