Namespace disappears when invoke is called

Question

I am sending the following SOAP message (I've abbreviated it ...):
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:open="http://www.openuri.org/" xmlns:pet="http://gencat.net/scsp/esquemes/peticion">
<soapenv:Header/>
<soapenv:Body>
<pet:Documents>
<pet:Document>
<pet:Hash xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:nil="true"/>
<pet:AlgHash xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:nil="true"/>
</pet:Document>
</pet:Documents>
I send the SOAP message like this:
public void send (Document xml)
  Node nReq = xml.importNode(req, true);
  xml.getDocumentElement().appendChild(nReq);
  SOAPEnvelope requestEnvelope = new SOAPEnvelope();
  SOAPBodyElement requestBodyElement =
    new SOAPBodyElement(xml.getDocumentElement());
  requestEnvelope.addBodyElement(requestBodyElement);
  Service service = (!signar) ? new Service() : new Service(getWssd());
  Call call = (Call) service.createCall();
}With Tcpmon I take a look at the actual message that is sent and Axis seems to automagically remove the 'xsi' namespace from both the 'pet:Hash' and 'pet:AlgHash' elements and adds it to the soapenv:Envelope element:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">.
I don't know why it's doing this (it's also adding the 'xsd' namespace) nor do I understand why the client I am sending it to can't process it, since it seems to be the same info, just sent in a different place. But they say they can't process it.
So I was wondering if there is a way to tell Axis NOT to change my namespaces around. I've been poking around the api and I don't see anything obvious.
Little help?
Thanks,
Bob

Answer 1

Hi,
We have developed our code using jdk1.4 and with jdmkrt. Now we are trying to upgrade to jdk 1.6. The methods already exists and it was working fine with 1.4.
The main difference is that the MBeanServer in 1.4 is is "com.sun.jdmk.MBeanServerImpl" and code is working properly with this. With 1.6 the server is taken as "com.sun.jmx.mbeanserver.JmxMBeanServer"