> From: A mailing list for Enterprise JavaBeans development
> [mailto:[EMAIL PROTECTED]]On Behalf Of Marcus Ahnve
> > 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.
>
> I totally agree.
Maybe the rule is too stringent (or too idealistic).
Such attempts have been made in the past :
- separating the UI from the data. Result : close to a complete success
(resource files in Windows, xrdb on X, etc...) but a minimal interaction
between both worlds is still necessary
- MVC. I still have to see a real-world MVC where the three units are totally
unaware of any private parts
The pattern here seems to be a separating entity that provides a certain amount
of separation but still needs to know a little bit about the two worlds it is
trying to connect. Entity beans seem to fit nicely in this role. The technology
is still young, explaining why they are maybe too much aware of both the model
and its user, but as time goes by, I expect the abstraction to become stronger,
although we will probably never reach a complete clean-cut abstraction.
The important is not so much the complexity of the barrier, but the ease with
which we can replace it with something simpler as progress is made.
--
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".
