Chris (and Berny):
With no intention of belabouring the issue, I wonder too if there is a place
for integration of any web app framework in a J2EE environment, if the
framework is meant to do that - the reason I ask is that although I use
Orion extensively for testing & verifying, I also use (and develop) the
Expresso web app framework - somewhat like Turbine in many ways, but with a
definite leaning towards the J2EE standard (e.g. JSP support, EJB
integration, etc). I'd like to get input on where people see such a
framework complimenting J2EE (if at all) so that we can focus our efforts in
the right places.
We've gone so far as to make a specific project on our site (Expresso EJB
project) that is specifically aimed at integrating Expresso in a J2EE
enviroment - and we've got some feedback, but would like more.
I'd be happy to take the conversation off-list, or onto our listserv for
Expresso ([EMAIL PROTECTED]) if that's better.
Thanks, and back to my usual quiet corner....
Mike
Jcorporate Ltd
http://www.javacorporate.com
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Christian Sell
> Sent: Saturday, September 16, 2000 12:00 PM
> To: Orion-Interest
> Subject: Re: Turbine on Orion
>
>
>
> >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
>
