Excel 2002 calling JBoss.NET Web Service

[christian.harms]

It's just so easy - at least up to doing a call without authentication and simple data types.

Did anyone implement a web service interaction between Excel 2002 and JBoss including authentication? I know that there is something on this in the tutorials as well but are any pitfalls waiting for me not mentioned there?

To share what I have learned so far on the topic:

The WIKI on JBoss.NET provides an overview (tutorials) and an example which I build and deployed to JBoss 3.2.5.

With JBossWS on JBoss 4 there is the J2EE compliant solution available. If I wouldn't want to go live with the service soon I'd go for that.

"Microsoft Office XP Web Services Toolkit 2.0" provides an extension to the VBA environment to locate web services and to generate VBA classes to access them. It's accessible in the VBA Editors extra menu. See http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnxpwst2/html/odc_cmplxtypes.asp for details and be aware that there is also a newer Version called "Microsoft Office 2003 Web Services Toolkit" which I didn't use so far.
See http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odc_wst2003_ta/html/odc_wstknew.asp

Using the toolkit it's a 2 minutes job to do the first call to the hello service.

[thomas.diesler]

jboss-4.x will be available end of 3Q2004, is this too late for you?

[christian.harms]

We are a small team and haven't prepared the change to JBoss 4 so far. We will not manage to switch before end of this year I guess. But you're right, it's time to start working on that.

Christian

[christian.harms]

Since I've got authentication working with the help of a former post (http://www.jboss.org/index.html?module=bb&op=viewtopic&t=51898)
and the "JBossNET with XDoclet" tutorial from the WIKI , I'd like to put my findings here:
1. I've followed the steps described in the tutorial on setting up authentication with XDoclet tags.
2. I've put the tag to the request-flow section as described in the post mentioned above.

Does anyone know what this is exactly implies?

3. I had to tell the SoapClient30 object that I'm using BASIC authentication on the server side, because it didn't found this out itself and to set username and password:
sc_HelloService.ConnectorProperty("WinHTTPAuthScheme") = 1
sc_HelloService.ConnectorProperty("AuthUser") = "test"
sc_HelloService.ConnectorProperty("AuthPassword") = "test"