Hi,
People designing applications built from EJB components often encounter
the following dilemma: their application contains some data (an entity
of their application model) that need to be shared among several
components/clients, but which is not persistent, how should they
modelize such data ?
- a stateful session bean instance, according to the EJB spec, should
not be shared by several clients,
- while an entity bean instance can be shared, but is persistent ...
Building a BMP entity bean "with no persistence" is not satisfying and
sometime not possible.
Are there some EJB design patterns describing how transient shared data
should be modelized ?
Thanks,
Best Regards,
Fran�ois
--
==================================================================
Fran�ois 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 "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
