[EMAIL PROTECTED] wrote :
| It is irrelevant for J2EE-1.4 compliant web services, it is good to have if
you plan to use an Axis client, which JBossWS is not.
Thanks Thomas.
The main goal is to use JbossWS WITH sforce.com ws and other already running
web-services from other 'vendors'. I'd
zeroman wrote : I'll try to ask for the 'J2EE-1.4 compliant web services'
example.
Looking at the post:
axis1.2 with tomcat 4 deployed in jboss4.01
http://www.jboss.org/index.html?module=bbop=viewtopict=61200
I'd like to ask one more thing.
Is it possible to 'mix' usage of Jboss.NET and JbossWS
anonymous wrote : The Axis example is irrelevant.
It is irrelevant for J2EE-1.4 compliant web services, it is good to have if you
plan to use an Axis client, which JBossWS is not.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3868848#3868848
Reply to the post
JBossWS is about portable J2EE compliant web services, which by definitition
should not have a dependency on a particular SOAP stack.
If sforce.com offers an example that uses standard J2EE WS clients, then this
is the one you want to use.
The Axis example is irrelevant.
View the original
zeroman wrote : I'm trying to use Jboss-4.0.1 Axis 1.1 for accessing
sforce.com WS.
| Thanks.
Just want add a little. When I use Axis 1.2RC2 standalone version the code
compiles and runs properly w/o any problems. Jbooss version 4.0.1, JDK 1.4.2.
Axis libs are taken from the:
