Hello Ulrich, > Fair enough, but be aware that this way you are making the servlet > engine the top container and embed an application server(*).
Yes, but ... when do expect Merlin to be a full-featured AppServer <g>? > 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. Yes again, but when I speak of integrating into a J2EE compiant servlet engine, this implies even WebLogic or WebShpere or other less known systems we have partner contracts ... these are the ones that we meet mainly in the real world. So basically, I have already full-blown appserver functionality, if I need it. > 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). Something like this is currently out of scope - at least in this form. Regards, J�rg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
