oh, before somebody worries.
THIS IS NORMAL XP PRACTICE.
It is called "refactoring".
First you eXtreme Program,
then you clean it good ...
marc
______________________________
"I want you to know tonight...
that we as a people,
will get to the promised land"
-- Martin Luther King JR --
______________________________
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of marc fleury
> Sent: Friday, July 07, 2000 11:49 AM
> To: jBoss Developer
> Subject: RE: [jBoss-Dev] setEJBObject
>
>
> Sorry to be answering my own mails, but as I pull the line on
> this one I end
> up with "most" of the container work done in the jaws plugin... (like
> calling ejbCreate and ejbPostCreate, dealing with the wrapper
> state etc etc)
>
> I am rewiring this (reaping out is a better word) work.
>
> About the only thing that should live there is the tuned updates
> stuff (was
> buggy yesterday, changed the if statement btw) and the rest should just be
> "just another web store" and not "just another container store".
>
> no biggy
>
> marc
>
>
>
>
> > -----Original Message-----
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]]On Behalf Of marc fleury
> > Sent: Friday, July 07, 2000 11:17 AM
> > To: jBoss Developer
> > Subject: RE: [jBoss-Dev] setEJBObject
> >
> >
> > just for the record...
> >
> > It is in fact done in the Jaws plugin now (which was indeed the "naive"
> > place given the codebase).
> >
> > it is done for create but wasn't done for find but I truly
> > believe that it
> > should NOT be done in the jaws plugin... what happens when we put
> > cocobase?
> > the entity of the EJBObject is not correctly set up by the
> > container and it
> > falls on the O/R mapper to do it??? yelch!!!!
> >
> > I will try to rewire/refactor this with the
> org.jboss.ejb.EntityContainer
> > class ... these expose the proper methods already (find and
> > createHome) and
> > must be the right place to do it... will check this improvement.
> >
> > marc
> >
> > _________________
> > "Victor, cleaner"
> > -- Nikita 1988 --
> > _________________
> >
> >
> > > -----Original Message-----
> > > From: [EMAIL PROTECTED]
> > > [mailto:[EMAIL PROTECTED]]On Behalf Of marc fleury
> > > Sent: Friday, July 07, 2000 11:03 AM
> > > To: jBoss Developer
> > > Subject: RE: [jBoss-Dev] setEJBObject
> > >
> > >
> > > never mind found it
> > >
> > > thanks
> > >
> > > marc
> > >
> > >
> > > > -----Original Message-----
> > > > From: [EMAIL PROTECTED]
> > > > [mailto:[EMAIL PROTECTED]]On Behalf Of marc fleury
> > > > Sent: Friday, July 07, 2000 10:34 AM
> > > > To: jBoss Developer
> > > > Subject: [jBoss-Dev] setEJBObject
> > > >
> > > >
> > > > is not set currently on the enterprise context, hence a bug.
> > > > The current TestBeans.jar chokes on that call to the environment in
> > > > entityCreate() (it's a method call not the ejbCreate()).
> > > >
> > > > For those familiar with the container interceptor, I am
> > > > struggling with the
> > > > exact place of where to put it.
> > > > Of course is was left out intentionally since it needs to
> > > happen on create
> > > > and find but also on multiple finds which is where it gets
> > confusing, i
> > > > understand the proper is the jaws plugin giving the current
> > > code base and
> > > > that really is f*cked up.. I mean the plugin for persistence
> > should not
> > > > touch the wrapper. It has to be in one of the invokeHome...
> > any ideas ?
> > > >
> > > > Please join me on bug #148
> > > >
> > > > marc
> > > >
> > > >
> > > > ________________________
> > > > Marc Fleury
> > > > Chief Technology Officer
> > > > Telkel, Inc.
> > > > ________________________
> > > >
> > > >
> > > >
> > >
> > >
> > >
> >
> >
> >
>
>
>
