> From: A mailing list for Enterprise JavaBeans development
> [mailto:[EMAIL PROTECTED]]On Behalf Of Adam Lipscombe
> 2. Using SessionBeans as a facade to an EntityBean.
>
> The EntityBean has the standard Create, Read, Update, Delete
> functionality.
>
> Taking the "session beans are actions, entity beans are objects"
> paradigm, how should I wrap the entity beans?
>
> Should there be 1 SessionBean for each action. e.g. separate
> "CreateItem", "DeleteItem" Session Beans?
> Or should there be one SessionBean with 4 methods?
I don't think this will buy you a lot since you are using StatelessSession
Beans. One bean with all the methods you need should be enough. After
that, it can either directly talk to an Entity bean if you are using pre EJB
2.0-PFD2 beans, or communicate with the back-end with value objects if you
are using local interfaces (PFD2).
--
Cedric
===========================================================================
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".
