In a well separated layer design, applicative layer should be independant of
persistance layer. So the use of a OODBMS or A RDBMS should not influate
modeling in the application layer.
Entity beans are clearly violating this separation rule. But from what i've
understood so far, session beans were designed to model process rather than
concept. Moreover, they have no persistance. So how can you use them to model
real-world entities ?
As they are powerful open-source RDBMS, and even hybrid DMBS available, this
question is important for people aiming public research project, rather than
e-business.
Le jeu, 02 mar 2000, vous avez �crit :
> You can use Entity Beans with OODB, but it is overhead and does not add
> value. Session Beans to pure objects is a very nice model. Very clean on the
> server side, and forces Service Based Architecture, which we think is a good
> thing.
Cheers
--
Guillaume Rousse
Iremia - Universit� de la R�union
15 avenue Ren� Cassin, BP 7151
97715 Saint Denis, messagerie cedex 9
Tel:0262938330 Fax:0262938260 ICQ:10756815
BRIDGEKEEPER: What... is the air-speed velocity of an unladen swallow?
ARTHUR: What do you mean? An African or European swallow?
===========================================================================
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".
