Re: [Axis2] Setting up Axis2 application with Jetty6

[Eran Chinthaka <ch...@opensource.lk>]

Hi Nicholas,

I do not see any problem with your deployment. Our model is to make 
Axis2 transport independent and it should be deployable inside any 
servlet container.

One of our release artifacts is a war distribution and you should be 
able to get it, drop it in to jetty and it should work.

Yes we had discussion on embedding jetty in to axis2 as the default 
transport listener, instead of simple http server that we use inside 
axis2. But that never happened. But if there is someone volunteering to 
do this, we are more happy to help.

Thanks,
Eran Chinthaka

Nicholas Hogg wrote:
> Hi,
> 
> I would really appreciate some feedback on how a project I am working
> has been set up - I suspect badly.  I have recently taken over the
> project and can make major changes if necessary.
> 
> - We currently run a Jetty6 web server standalone.
> - We build our axis2 based webservice using maven2, building with a
> compile time dependency of the axis2-adb artifact.  This dependency is
> required for two reasons:
>     1. To compile adb generated service code.
>     2. For deployment in Jetty (see below).
> - We deploy by packaging the webapp as a WAR file, complete with
> axis2-adb classes, and drop that WAR file into Jetty's webapps directory.
> - The webapps WEB-INF/web.xml has:
> <servlet>
>   <display-name>Apache-Axis Servlet</display-name>
>   <servlet-name>AxisServlet</servlet-name>
> <servlet-class>org.apache.axis2.transport.http.AxisServlet</servlet-class>
> </servlet>
> 
> And it maps requests to the AxisServlet with:
>     <servlet-mapping>
>         <servlet-name>AxisServlet</servlet-name>
>         <url-pattern>/services/*</url-pattern>
>     </servlet-mapping>
> 
> - So request comes in, Jetty receives it, passes it off to the
> AxisServlet, which passes it off to our implementing service class.
> 
> This is quite different to information in the Axis2 Installation Guide,
> where the options seem to be:
> 1.  Install Axis2 as a standalone server and deploy webapps to it.
> 2.  Install the Axis2 web application to a servlet container, and deploy
> webapps to it.
> 
> My questions are:
> - 1.  Is there a good reason why I should the way we deploy our webapps
> in Jetty?  ie are there things in axis2 we are missing out on because of
> the way we deploy?
> - 2.  There was talk on the developers mail list about a year ago about
> using Jetty as Axis2's default container, due to load problems using the
> existing simple HTTP server.  Did this happen?
> 
> My gut feeling is that Jetty is a best container for us to be using.  If
> there were a way for axis2 to use Jetty then we could run axis2 standalone.
> 
> Any comments are greatly appreciated.
> 
> Regards,
> Nick



---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org