> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Rickard �berg
> Sent: Sunday, July 09, 2000 1:01 AM
> To: jBoss Developer
> Subject: Re: [jBoss-Dev] setEJBObject
>
>
> marc fleury wrote:
> > > -1. Doing these calls in EntityContainer won't work. Motivation:
> > > * There is a difference in semantics of these calls between
> BMP and CMP.
> > > The only part that knows if we're doing BMP or CMP is the persistence
> > > manager. Hence the persistence manager must make these calls. The
> >
> > wrong.
> >
> > exposing CMP or BMP with metadata is trivial really.
> > And then we can do the right thing re: implementing EJB calls
> in the right
> > place.
>
> If you want to change this then the container callbacks will be spread
> all over the place, and the EntityContainer wont be making all of them.
> For example, the cache calls the PM to activate instances, and currently
> the PM calls "ejbActivate". If you want to change that along the above
> lines, then the "ejbActivate" call goes into the cache instead. What
> would be the point of that?
>
> > Don't make a big architectural decision such as "all ejb calls will be
> > called by the persistence engine" based on the fact you don't put the
> > relevant information in the right place.
>
> The PM should deal with the semantics of the create, and I thought that
> this was one aspect of it. As above, I also wanted to keep
> EntityContainer as simple as possible.
>
> > > persistence manager also makes all the other calls so this is nothing
> > > new.
> > > * EntityContainer is glue only. It should not do any actual
> work. All it
> > > does is delegate to other parts to do the actual work.
> >
> > wow, JAWSPersitenceManager.java is "container" but
> EntityContainer.java is
> > "glue"?????
>
> No, JAWS implements the persistence semantics, and EntityContainer is
> the logical view of a bean. But yes, for the most part EntityContainer
> is glue. COME ON. This is something that we have advocated from the
> beginning. Everything that is related to algorithms of some kind is
> pluggable. This is the core idea of the entire jBoss 2.0 architecture.
> You don't agree? Dude, sometimes I feel sooo lonely.
>
> > wow, you can't be serious.
>
> Very serious. IMHO your above ideas are degenerating the entire
> architecture. Depressing to say the least. I thought you had understood
> what I wanted to do here. :-(
RICKARD WHAT ARE YOU TALKING ABOUT?
Putting the EJB CALLS IN JAWS IS NOT ARCHITECTURE, IT"S POOPOO CODE. IT
NEEDS TO MOVE OUT OF JAWS.
marc
>
> /Rickard
>
> --
> Rickard �berg
>
> @home: +46 13 177937
> Email: [EMAIL PROTECTED]
> http://www.telkel.com
> http://www.jboss.org
> http://www.dreambean.com
>
>
