JBossWS and C# Interoperability

[omatzura]

Hi!

I suggest you start by creating your wsdl "manually" so it conforms to .net, jbossws and basic-profile requirements, then validate the wsdl with .net (by importing it) and finally use wscompile -import to generate jbossws server stubs.. this has been our approach and it works "just fine" (ahem)..

good luck!

/Ole

[jason.greene]

FYI,

Microsoft will incorporate rpc/literal in the 2.0 .NET framework release. It is currently available in 2.0 Beta 1, although I haven't had time to test it out.

-Jason

[thomas.diesler]

Ole, what are "jbossws server stubs"? Maybe there is something lost in translation. AFAIK, the term stub refers to the client side, and even then we don't have them. Instead we use dynamic proxies on the client. All that is generated from wsdl is:

- service endpoint interface (SEI)
- optional service interface (SI)
- optional complex user types
- optional user exceptions

wscompile generates stubs, but they are propriatary to the jwsdp and are useless for WS4EE

[didi]

I am experiencing the same problem ("Namespace URI cannot be null") and I tried to create a webservice using the jboss documentation (http://docs.jboss.org/jbossas/jboss4guide/r2/html/ch12.html). I also used the recommended wscompile over AXIS Java2WSDL...

I am using JDK1.5.0_01 with jboss-4.0.1sp1 on a SuSE 9.2 linux. If it helps you I could post the exception shown in the jboss log.

[md5georg]

Didi,

Installing 4.0.2 solved my "Namespace can not be null" problems. You can find a RC1 of the 4.0.2 here:

http://sourceforge.net/projects/jboss/


Best regards,

Georg

[hjones]

(I'm the guest from above)

I got rid of the null-namespace-exceptions as suggested above wit JBoss 4.0.2RC1. Using the document/literal style finally made C# speak to the SLSB-Web Service. I didn't use the wscompile-generated RequestStruct-wrappers as they generate namless long_1, string_2, Date_3 members only. Everytime I had more than one Web Method parameter I created an own container class. However, this leads to an additional indirection on the C# side but it increases readability.

Thanks for the replies.

[md5georg]

I found this insightfull blog regarding the "one-parameter" choice. I guess this is one side of the camp (as the author writes), but if it gives me lesser problem with interoperability it will continue to be my choice in the future...


http://blogs.msdn.com/donsmith/


Best regards,

Georg

[didi]

thanks a lot md5georg, I got my webservice working ... well at least the namespace error message is not coming up anymore. But: I tried http://www.soapclient.com/soapTest.html to interact with my webservice and another error is coming up. Even though I followed the jboss tutorial and the JAXRPC- as well as the DII client are working I am not sure if it works with other programming languages. Does someone know an online-soap client (like the one mentioned above) or does someone know a soap client which I can just download, install and use? It should not be a java client and preferebly should be for Windows. Thanks in advance!