Alex Blewitt wrote:
I also think that whilst some choice is good, too much can be detrimental. What I'd like out of an EJB server is one that 'Just Works' and I wouldn't be particularly bothered whether it used Tomcat/Jetty or OpenEJB/OJB. Nor would I (as an admin) bother about changing it.
With respect to the web container, it is my intention to contribute by writing abstract webcontainer and webconnector services.
I want to capture 99.999% of the common configuration and management of the web tier in these services - so that you do not need to know what underlying implementation will be (unless you really care). There should be no need to have web container specific configuration in the standard deployment. Services such as distributed sessions, single sign-on, and load balancing management should be able to be written to work with any web container.
My first implementation of these will use Jetty, but a Tomcat version I assume will follow if there is call for it. As to what should be the default and what get's certified... I'm way too biased to comment on that.
cheers
-- Greg Wilkins<[EMAIL PROTECTED]> Phone/fax: +44 7092063462 Mort Bay Consulting Australia and UK. http://www.mortbay.com
