cannot call jboss ws from MS SOAP SDK

[ybenigot]

When using a VB Client (VB 2005/MS SOAP SDK 3.0) to jbossws (v1.0.3 which comes from jboss 4.0.5) the parameters are not correctly passed

when jbossws waits for a parameter named String_1,
it receives a parameter named SOAPSDK1:String_1 ,
and followed by xmlns:SOAPSDK=<url to ws namespace>

jbossws rejects this as a SOAP fault

There is a workaround which is to use MSSOAP lowlevel API
as described in a former post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3966085

I guess that this xmlns construct is authorized by the specifications,
and that jbossws should be configured to accept it. Is that correct ? Is there
a clean way to use the M$ high level API ?

[centecbertl]

Clients using the .net sdk 2.0 work for Services using doc-literal-wrapped services generated by jbossws 1.0.x on jboss 4.0.5 for me so far. I did not try the .net 3.0 sdk so far.

Your could try to switch to doc-literal (if you are not already using this style) or using the .net 2.0 sdk (Is it possible to use them in parallel?)

[peterj]

Not sure if this would fix your problem, but could you move up to jbossws 1.2? I have a 1.2 web service working correctly with a .Net 3.0 C# client, using both doc and rpc style.

[yves.benigot]

I tried jbossws 1.2 installed on top of jboss 4.0.5 without success : I get the same error.

I will try C# now to see if it works better with jbossws

I didn't try the doc-literal yet, I will do it also.

[yves.benigot]

Finally I tried wstools with style=document

Visual Basic cannot get along with this.

It seems that MS SOAP Toolkit is using rpc style, and that the high level API uses a namespace in the parameter definition, which is incompatible with jbossws. However, since this toolkit is superseded by .Net there is no way
around.

The conclusion is : one must use the call Serializer.SoapAttribute("xmlns", "", "", "") and the low level API to get it work.

With C#, on the contrary, everything goes fine, and a webservice call is two lines of code.

[monowai]

Haven't tried your specific example, but have had no problems calling webservices from Excel. Here be the link I used to get things going.

http://www.windowsdevcenter.com/pub/a/windows/2005/02/08/xcel_mm.html

Maybe there will be some clues in the MS generated code.

[sandello]

I think, this is the bug.
I have posted it to the Jira
http://jira.jboss.com/jira/browse/JBWS-1712