4 Replies Latest reply on Feb 22, 2006 3:37 PM by Thomas Diesler

    JBOSS and .NET WS Interoperability??

    Anson Smith Newbie

      I hava a strange problem. I cannot write a j2ee client that can successfully call an .NET WS. If I write a standalone java client it works fine and this is the SOAP msg that is sent to the .NET Service

      <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"
       xmlns:ns1="http://WHATEVER.net/">
       <soapenv:Body>
       <ns1:GetTasks>
       <ns1:projectName>Infrastructure</ns1:projectName>
       </ns1:GetTasks>
       </soapenv:Body>
       </soapenv:Envelope>
      


      But if I write a JBOSS j2ee client it will not work and this is the SOAP msg that is sent

      <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">
       <soapenv:Body>
       <ns1:GetTasks xmlns:ns1="http://WHATEVER.net/">
       <projectName>Infrastructure</projectName>
       </ns1:GetTasks>
       </soapenv:Body>
       </soapenv:Envelope>



      WHATEVER is NOT the actual NameSpace

      The problem is that the projectName parameter is not nameSpace qualified. Is this a problem with JBOSS or is .NET unreasonable in expecting child elements of the operation to also be nameSpace Qualified??

      I am stumped, any help would be appreciated.

      Anson Smith