----- Original Message -----
From: "Geert Mergan" <[EMAIL PROTECTED]>
> - can anyone give me one or more good reasons to go for entity beans? They
> seem like a bad solution from everything I read so far in various resources
> on the net..
There seem to be many people on this mailing list that have problems with entity
beans, but most often they don't seem to have any real evidence. It is more like
an urban myth. :)
I think Entity beans are a good mechanism to represent a persistent business
object. Many of the "problems" that developers have with entity beans center
around things like concurrency control and the complexity of coding
course-grained beans. Unless you are using an EJB 2.0 (maybe it won't be until
3.0 until this is actually made easier) implementation or some complicated
framework (TopLink), this will always be a complicated task.
> - If I understand well, Sun's JDO spec has not yet been implemented so while
> waiting for such an implementation, do you think Castor's JDO is a good
> alternative + why (not) , eg. does it follow part of the Sun JDO spec?
Perhaps you have looked at JDO and can enlighten me. What will JDO get you that
CMP doesn't already offer? I view JDO as a declarative persistence framework.
The same challenges face the developer that uses JDO as the developer that uses
Entity Beans. JDO seems like a good alternative for persisting objects *outside*
of the EJB framework, but if you know you will be using EJBs, why bother?
jim
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
