Hi,
a complementary information related to our discussion of the beginning
the week. A very interesting article on the design of entity beans...
Not so easy ... EJB2.0 persistence (with relationships and dependent
objects) should help ...
http://www.sdmagazine.com/articles/2000/0004/0004c/0004c.htm#
Best Regards,
François
[EMAIL PROTECTED] wrote:
> > Therefore what is recommended is to build session beans,
> > that will aggregate operations on entity beans, and return
> > the whole data needed by the client. You may also define
> > methods on the entity beans that return a bunch of data
> > instead of EJB references (as finder methods do).
> ...
> Returning a bunch of data is also only a workaround: It's neither object oriented
>design, nor is it transparent to the
> application developer.
--
==================================================================
Francois EXERTIER Evidian (Groupe Bull)
1, rue de Provence, BP 208, 38432 Echirolles cedex, FRANCE
mailto:[EMAIL PROTECTED]
http://www.evidian.com/jonas http://www.objectweb.org/jonas
Tel: +33 (0)4 76 29 71 51 - Fax: +33 (0)4 76 29 77 30
==================================================================
----
To unsubscribe, send email to [EMAIL PROTECTED] and
include in the body of the message "unsubscribe jonas-users".
For general help, send email to [EMAIL PROTECTED] and
include in the body of the message "help".
