"Diethelm Guallar, Gonzalo" wrote:
> I have a definite feeling that EJBs
> are not really required for 90% of the cases, and that a well
> structured servlet (Turbine), plus all kinds of services (Turbine),
> plus what we call "connectors" to data back-ends, fit the bill nicely.
> One point where I do see a place for EJBs would be if you had to
> coordinate a transaction across multiple data back-ends; in this
> case, two-phase commit would be invaluable. Since this case doesn't
> really come up that often, the current reality is that we just have
> not used EJBs at all, ever.
I fully agree with you. EJBs will come handy while developing apps
that depend on transactions heavily, like financial, e-shops and such.
Most of the websites don't have and don't need that.
Rafal
--
Rafal Krzewski
Senior Internet Developer
mailto:[EMAIL PROTECTED]
+48 22 8534830 http://e-point.pl
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
