Hey
"Hardy, Patrick, DDI - Garden City" wrote:
> What I don't understand is that it creates an abstract class that a CMP or
> BMP class would implement. The abstract class contains all of the business
> methods and required methods that must be implemented from the EntityBean
> class. Why this additional layer of abstraction? Is this defined in a
> specification somewhere? Aren't the only classes required are home, remote,
> and bean classes for an EJB? Why should an additional abstract class be
> implemented by the bean class?
>
> Has anyone here used ejbDoclet before?
Better yet, I wrote it :-)
The EJBDoclet allow you to use the EJB 2.0 CMP style, which means that
the bean provider writes abstract EntityBeans, with abstract get/set
methods for all persistent fields. EJBDoclet then generates a concrete
subclass which is EJB 1.1 compliant, which is thus deployable in an EJB
container.
If you have any further Q's on EJBDoclet, please use the EJBDoclet
mailing list at sourceforge.net/projects/ejbdoclet.
regards,
Rickard
ps. BTW, you got it backwards: YOU create an abstract class, and
EJBDoclet creates a concrete subclass of it.
--
Rickard Öberg
Email: [EMAIL PROTECTED]
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
