yes, I've successfully done that. But ..
1. I cannot use axis beta3. I always get the "the targetService is null" error, so I tried the nightly drop of 08/09/2002 and it works.
2. I don't use jboss.net provider. I use Axis EJB provider and it works just fine.
I'm new to jboss.net and my perception is that jboss.net is Axis.
What's the difference between jboss.net & Axis EJB provider ?
I am quite new to these things too. However, AFAIK, jboss.net has it own way to deploy webservice while using axis engine. Both of them have the same target but different way to use.
I myself prefer axis since it is less proprietary. Theoretically, I should be able to use axis with any J2EE-compliant container while jboss.net can be used only in JBoss.
This is interesting for me because we yesterday started a project that needs WebServices (SOAP) and I'm about to create the architecture and design.
If I decide to use Axis instead of JBoss.NET, how do I install Axis on JBoss? Will I have to disable JBoss.NET?
Axis is the central core of Jboss.Net... You need it for web services processing.
I was wondering if you, or anyone else, managed to get the new release of Axis working with JBoss 3.0.2.
How do you replace the JBoss-Net service with an straight Axis one that provides equal functionality and ease.
I am using JBOSS 3.0.0 and want to replace the beta version of axis with the new 1.0 version.
Can this be done?
Or is is a customized version of axis. If not then do I just drop the axis.jar file in the \server\all\lib directory and remove the old one?
I am on Windows 2000 server.
I saw a message from cjung indicating that the jboss.net code in HEAD was updated to use Axis rc1. So I would think that you should be able to use Axis release 1.0 by just replacing the Axis jars, assuming no api changes between RC1 and final release.
The support for Axis RC1 has not yet been backported to Jboss 3.2. This means that it is probably not in Jboss 3.0 either. The CVS HEAD is currently dev version 4.0.