>I would appreciate if you could tell me about (OpenSource) choices you
>mentioned.
I am referring to opensource J2EE implementations. There are a few, not all
of them implementing full J2EE (but then, you may not need the full scoop).
Here's a short list: Apache Tomcat, Enhydra, EJBoss, OpenEJB, Resin(?). On
top of J2EE, I prefer to have a framework that incurs as little overhead as
possible and does not overlap or conflict with the underlying architecture.
>But to give you an answer on why anybody would install Turbine on a J2EE
>server: Performance to serve clients is one answer. Servlets are part of
>the J2EE, too. Why always going via EJBs and not serving the client via
>a pools and servlets.
I was not referring to EJB. EJB and Turbine have little overlap, although I
am not sure how well they integrate. JSP is more of a problem, and I really
dont like the sometimes (in my view) arrogant statements that are being made
in that respect (not yours). We have a standard, and I think its a good one
that gives you all the flexibility you need.
ok, so much. Lets not get ideological over this, though. There's room for
everyones preferences...
regards, Chris
