Schaible, J�rg wrote:
Hi Ulrich,> since Sevak does integrate Tomcat into Phoenix, I know that this is
while I recognized Phoenix as Avalon container, I did not have alook at Sevak. But,
> not the way we want to go. We have to integrate our webapp into different J2EE
> servlet engines and we will normally not have the control over it.
Fair enough, but be aware that this way you are making the servlet engine the top container and embed an application server(*). Sevak means that the application server is the top container and embeds a servlet engine (Tomcat, Jetty or Jo! at this point).
Since an application server can not only run servlets, but also generic server applications, it is IMHO more sensible to make it the top container. Servlets are just specialized server applications.
Also, from application servers one can expect operational support to manage lifecycle etc. of the applications via a management console. This is something which servlet engines rarely provide and, I believe, never in a standardized way (JMX).
cheers,
Ulrich
(*) Merlin at this point is not a full-featured application server, but according to the roadmap it or its successor will be one.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
