Chris
 
Thanks for the reply. I really have no control over the server. It is up and running and working correctly.
The problem is with my client request. Those "nsx" tags are the problem. I don't understand why Axis
put the "nsx" in there by default. If I knew why they are put there automatically, I may be able to figure
out how to tell axis to not do it.
 
----- Original Message -----
From: chris
Sent: Monday, February 02, 2004 11:28 AM
Subject: RE: How to remove "ns1" from Custom Header

The server is attempting to deserialize the request and is looking for a map between the XML QName and a Java object.

 

Register a Java object on the server corresponding to http://openuri.org/2002/04/soap/conversation/:StartHeader, and the server will not fault.

 

/Chris

 

-----Original Message-----
From: Greg Pedder [mailto:[EMAIL PROTECTED]
Sent: Saturday, January 31, 2004 6:47 AM
To: [EMAIL PROTECTED]
Subject: How to remove "ns1" from Custom Header

 

Hello all. I have a WSDL file that I then an WSDL2Java against to generate the client stubs.

Unfortunately, the subs for the custom header did not get generated so I am trying to add one

manually.

 

SOAPHeaderElement myheader = new SOAPHeaderElement("http://openuri.org/2002/04/soap/conversation/", "StartHeader");

try {
      myheader.addChildElement("conversationID").addTextNode("GSP-6555555555");
}
catch(javax.xml.soap.SOAPException se) { }
stub.setHeader(myheader);

When I add the following code and send off the requst, I see the following being received by the server:

 

 

<soapenv:Header>
<ns1:StartHeader soapenv:mustUnderstand="0" xmlns:ns1="http://openuri.org/2002/04/soap/conversation/">
<ns1:conversationID>GSP-6555555555</ns1:conversationID>
</ns1:StartHeader>
</soapenv:Header>

 

I am not setting "ns1" anywhere, so I assume Axis is automatically putting it there. How can I remove all references to

"ns1"? Having the "ns1" there is causing the server to ignore my request. Thanks in advance

Reply via email to