4 Replies Latest reply on Feb 22, 2006 3:37 PM by thomas.diesler

JBOSS and .NET WS Interoperability??

anson.smith Feb 17, 2006 5:32 PM

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

1. Re: JBOSS and .NET WS Interoperability??

thomas.diesler Feb 20, 2006 4:59 AM (in response to anson.smith)

It depends on the value of the elementFormDefault element if it is a document/literal service. If it is rpc/literal JBWS-706 might apply

http://jira.jboss.com/jira/browse/JBWS-430
http://jira.jboss.com/jira/browse/JBWS-474
http://jira.jboss.com/jira/browse/JBWS-706
Actions
2. Re: JBOSS and .NET WS Interoperability??

anson.smith Feb 20, 2006 11:06 AM (in response to anson.smith)

The .NET WS is document/literal. I am using JBOSS WS 4.0.3. I downloaded 4.0.4 and It didn't seem to fix the problem. elementFormDefault value is set to qualified in the .NET WS WSDL. Could you give me an example of how to use the ws4ee-deployment.xml file, As there are 4 other webservices deployed in this WAR file. I just can't believe I am the only one having this problem If someone could point me in the right direction it would be greatly appreciated.
Actions
3. Re: JBOSS and .NET WS Interoperability??

anson.smith Feb 20, 2006 12:03 PM (in response to anson.smith)

"Anson.Smith" wrote:
The .NET WS is document/literal. I am using JBOSS WS 4.0.3. I downloaded 4.0.4 and It didn't seem to fix the problem. elementFormDefault value is set to qualified in the .NET WS WSDL. Could you give me an example of how to use the ws4ee-deployment.xml file, As there are 4 other webservices deployed in this WAR file. I just can't believe I am the only one having this problem If someone could point me in the right direction it would be greatly appreciated.

Also, this is just a WS Client that I am trying to develop so there is no wsdd generated. Could this be causing a problem?
Actions
4. Re: JBOSS and .NET WS Interoperability??

thomas.diesler Feb 22, 2006 3:37 PM (in response to anson.smith)
tdiesler@satellite /cygdrive/d/projects/jboss-branch/jboss-4.0.x/testsuite/s rc/resources/webservice $ find . -name ws4ee-deployment.xml ./jbws153/WEB-INF/ws4ee-deployment.xml ./jbws168/WEB-INF/ws4ee-deployment.xml ./jbws414/WEB-INF/ws4ee-deployment.xml ./jbws424/WEB-INF/ws4ee-deployment.xml

Using ws4ee-deployment.xml is not something we recommend and is but a neccesary hack to work arround the problem that axis does not look at the schema.

You are probably better of using jbossws our new schema aware stack that will be available in jboss-4.0.4

http://wiki.jboss.org/wiki/Wiki.jsp?page=WSDeployJBossWS
Actions

Go to original post