I can't say that I know to 100% how, but I have managed to have my JBoss running and at the same time be able to look at my SOAP Admin Client over http://localhost:80/soap/admin/index.html (I've changed the port from 8080 to 80).- First of all, my deployed Web Services didn't exist any more, so I had to deploy a new one. Why did that happen?- Then I went to http://localhost:80/fibo/index.html, where my App is running, gave some input and pressed the button to get my answer over the Servlet, Bean etc. The problem is, it looks like he hasn't found the SOAP service, as though it is not deployed or as though it is wrongly deployed. So I get a null pointer exception, and if I ask SOAP for some output I get this::[Header=null] [methodName=null] [targetObjectURI=null] [encodingStyleURI=null] [SOAPContext=[Parts={[cid:null type: text/xml; charset=utf-8 enc: null]}]] [fault=[Attributes={}] [faultCode=SOAP-ENV:Server.BadTargetObjectURI] [faultString=Unable to resolve target object: buch.kapitel7.soap.BeispielServer_1] [faultActorURI=/soap/servlet/rpcrouter] [DetailEntries=] [FaultEntries=]] [Params={}]Does anybody know what I have to do?Do I have to put classes or something else somewhere special in the JBoss directory?Can somebody help me or should I provide some more information?

I'm running on Windows XP, Eclipse as an IDE and I am using JBoss 3.0.7 in a bundle with Tomcat 4.1.24. Are other versions easier to use?I don't use Axis or JBoss.NET, I thought JBoss, Tomcat and my SOAP RPC Router and Admin are enough. Would it make my life easier using one of these two or may I do without?Thanks for your interest,Kosta

Apache Axis is a follow up of Apache SOAP. I think that you definetly need to upgrade to that one if you need latest features and support.

Jboss 3.2.2 is out and offers quite cool features but if you have no problem with 3.0.7 I wouldn't suggest to upgrade in a first place.

JBossNET is a wrapper around Apache Axis for JBoss. Unfortunatetly, JBossNET is not available with your version as far as I know.

Changing to 3.2.2 will be a big change for you as configuration files have changed a little bit.

In a first place what I suggest to you is to rollout your application to Apache Axis.

Download the axis distribution and takes the webappes directory. You'll find a folder named axis, rename it to axis.war so that Jboss can deploy it as a war application.

Copy this axis.war to your deploy directory. Now you have your Admin and RPC router ready (actually the RPC router is now a servlet, named AxisServlet, check http://localhost:8080/axis for more details)

As you said, I downloaded Axis, renamed the webapps/axis to webapps/axis.war and copied it to my Jboss server's deploy directory. On starting JBoss I can now call http://localhost:8080/axis and see the Axis page, which looks like that:_______Hello! Welcome to Apache-Axis.

What do you want to do today?

Validate the local installation's configurationsee below if this does not work.View the list of deployed Web servicesCall a local endpoint that list's the caller's http headers (or see its WSDL).Visit the Apache-Axis Home PageAdminister Axis[disabled by default for security reasons]SOAPMonitor[disabled by default for security reasons]To enable the disabled features, uncomment the appropriate declarations in WEB-INF/web.xml in the webapplication and restart it.Validating AxisIf the "happyaxis" validation page displays an exception instead of a status page, the likely cause is that you have multiple XML parsers in your classpath. Clean up your classpath by eliminating extraneous parsers.If you have problems getting Axis to work, consult the Axis Wiki and then try the Axis user mailing list.--------------------------

First of all I did as they say, went to the WEB-INF/web.xml in the axis.war and uncommented the one commented section, without that changing anything. If I now press "Administer Axis" I get a page with following message:_______Server is runningCurrent load = 1-----------

More questions...:- My application file is called FiboApp.ear, I just deploy it to my running JBoss, is that right?- Inside that application I call a deployed service, but the problem is that in Axis I don't know where to deploy it...Do I have to put the classes somewhere special?- What do I get by using Axis instead of SOAP?

I think I am a little confused, but I am really thankful for your help!

Although I went to the WEB-INF/web.xml in the axis.war and uncommented the one commented section, that didn't change anything. The Axis page still says that"Administer Axis[disabled by default for security reasons] "

If I press "Administer Axis" I get a page with following message:_______Server is runningCurrent load = 1-----------

Stephane, thanks again for your help and I hope I haven't tired you...I hust don't seem to be able to deploy services with axis, in every tutorial I have read that I should do it like:java org.apache.axis.client.AdminClient deploy.wsddWhen I do that, I just get a NoClassDefFound Error...Any Ideas?

I think I have all of the axis jars in my classpath (actually I found out somewhere that I can put them in a special environment variable called AXISCLASSPATH).Usually I use ant through Eclipse, but I could also use it as standalone, your idea with the task sounds good. When you say remotely, can it be on the same computer? Do you want to send it to my email?