Re[2]: Problems deploying with AdminClient

[Martin Wunderlich]

And at last I seem to found the reason for the disappearing web
service, albeit not the root cause. This post here
https://bugs.eclipse.org/bugs/show_bug.cgi?id=118673 gave me the idea
of checking the file WEB-INF/server-config.wsdd. And indeed, there was
no description of the deployed service at all! So, I copied over a
backup copy of this file, restartet the server and everything's working fine 
again.
I have
no idea, why the service description disappeared in the first place.
Might be related to the auto-deployment of the web-app using
(My)Eclipse.

CHeers,

Martin

> Testing a bit more I was able to successfully deploy a different web service 
> to a
> different location on the same Tomcat installation. Then I copied all
> the resources to a new project (in Eclipse), which I deployed to a new
> web-app and things seem to work there. So, at least I
> have the problem limited down now to the original service that I
> wanted to deploy. Still, it's puzzling...

> In the process, I happened to notice that the SOAPMonitor tool can
> only be used, if Tomcat is installed on port 8080. Is there a way to
> change the port to 80? It reverts back to 8080, even if I call the
> SOAPMonitor with http://localhost/

> Cheers,

> Martin

Re[2]: Problems deploying with AdminClient

[Martin Wunderlich]

Hi Siamak,

Thanks a lot for the suggestion. I am still using Axis 1.3, so it
wouldn't be related to Axis 2, I guess.

Cheers,

Martin

> Hello Martin.


> As far as I know the AdminClient was used by Axis to deploy a service.
> With Axis2 the deploying has slightly changed.

> Please go through the User's Manual to see how to deploy a service.

> http://ws.apache.org/axis2/1_0/userguide.html

> You will see that you have some options:
> 1) create an aar-archive and put it in the WEB-INF/services directory of
> the axis2 webapp
> 2) create an aar-archive and upload it through the Administration UI
> 3) place the content of the aar-archive "unpacked" into the 
> WEB-INF/services/${YOUR_SERVICE} directory

> The third option is usefull if you have a lot jars placed in the 
> lib-directory of you service because the Axis2 ClassLoader is very slow
> while loading jars inside aars ;-)


> I hope I could help you,

> Siamak Haschemi