What ever servlet engine it is JBoss or Tomcat or ......
Axis2 is something for Tomcat or JBoss or ....
so you deploy AXIS2.WAR to one of this
servlet-engines
Axis2 is a message processing engine doing all for you that you can deploy
web-services so you deploy AXIS2 Webservices TO AXIS2 in a .AAR files
Given AXIS2 is running, and given AXIS2 is configured for HOT DEPLOYMENT any
time you compile/pack/copy your webservice.aar
into the service dir of AXIS2 makes AXIS2 re-deploying your web-service.
>From this view point I can't see any difference; bee it Tomcat or JBoss or ...
>servlet engin, it's AXIS2 which does the re-deployment of webservice
and not Tomcat or JBOss or any other servlet engine.
In short. Once you have deployed AXIS2 and it's engine is ready, to then
re-deploy a web-service does not require any re-deployments AXIS2
AXIS2 depends on a working servlet engine while web-services depend on a
working AXIS2-engine
Josef Stadelmann@
axa-winterthur.ch
-----Ursprüngliche Nachricht-----
Von: Vinh Nguyen (vinguye2) [mailto:[EMAIL PROTECTED]
Gesendet: Mittwoch, 9. April 2008 05:11
An: axis-user@ws.apache.org
Betreff: RE: web service deployment options
Looks like you mentioned JBoss in your original email:) In JBoss, apps are
temporarily unpacked and run from a location like to:
\jboss\server\default\tmp\deploy\*
If you place anything into this folder, it will be cleared upon the next
restart.
_____
From: Vinh Nguyen (vinguye2)
Sent: Tuesday, April 08, 2008 8:07 PM
To: axis-user@ws.apache.org
Subject: RE: web service deployment options
Hi,
Make sure your .aar is packaged inside the "original" Axis2 dir/war deployment.
I'm not sure what type of app server you're using, but if your AAR is
disappearing, then you're probably putting it inside some "runtime" deployment
of Axis2 that the server recreates each time the server starts. Hence,
anything placed into this temporary location will be gone upon restarts.
-Vinh
_____
From: Nate Roe [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 08, 2008 4:54 PM
To: 'axis-user@ws.apache.org'
Subject: RE: web service deployment options
I don't know what I did differently, but this is not the case for me. When I
was using AAR deployment, bouncing JBoss would never un-deploy my AARs.
_____
From: Dennis Sacks [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 08, 2008 4:45 PM
To: axis-user@ws.apache.org
Subject: Re: web service deployment options
Great info! Thanks for alerting me to that.
Does anyone know however, if I do want to use the axis2 web application, is
there a way to make a deployed service persist through an application server
restart?
Now, when I bounce JBoss, I must reload my webservice .aar file, as the service
is no longer there.
Dennis
On Tue, Apr 8, 2008 at 3:27 PM, Nate Roe < [EMAIL PROTECTED]> wrote:
Dennis,
Here's a KB article that I used to learn to deploy Axis2 as part of my web
application under JBoss:
http://wso2.org/library/90
Regards,
Nate Roe
_____
From: Dennis Sacks [mailto: [EMAIL PROTECTED]
Sent: Tuesday, April 08, 2008 3:06 PM
To: axis-user@ws.apache.org
Subject: web service deployment options
Hi,
I'm curious how people typically deploy axis2 web services? Does everyone
install the axis2 web application and deploy using that? Are there other
options?
When I stop and restart JBoss (the app server I'm using), I have to upload my
web service into the axis2 web application again. Is there a way to avoid
having to do that?
Dennis
