I disagree that such is a missing feature. Could you please elaborate - maybe I
haven't come across a scenario where it would be useful... I consider activation and
when to do it to be a specific feature of the container and I don't want to think
about it as a bean developer, but that may be a bit naive :)
Peter, let me know if I understand correctly: you are looking for a way to incorporate
test hooks so that you can verify adherence to the spec for re-establishing the bean
state when activated; as opposed to a more general desire to be able to
programmatically activate or passivate a bean at any time. If you are looking for the
former, would it be valid to create a specific InstanceCache specifically for testing
that would just passivate after a certain condition (i.e. 10 seconds after activated,
immediately after activated...)?
I spent a little time looking org.jboss.ejb.plugins.RandomEntityInstanceCache to see
how it works. I think that my idea above would be easy to implement if it is what you
are looking for.
If anyone has worked on the bean caches before - please correct if I am off-course...
- jeremiah
------Original Message------
From: Adi Lev <[EMAIL PROTECTED]>
To: jBoss Developer <[EMAIL PROTECTED]>
Sent: June 29, 2000 5:05:49 AM GMT
Subject: RE: [jBoss-Dev] EJB passivation/activation
I agree, This is a missing feature.
There should be passivate and activate (or pause resume) for the container
(the server)
You can now only do it by shuting down the server.
This is an Admin request type and not a statndard user client. In
implenation our Servers
we use pause resume which is similar in concept.
> -----Original Message-----
> From: Peter Braswell [SMTP:[EMAIL PROTECTED]]
> Sent: Thursday, June 29, 2000 6:16 AM
> To: jBoss Developer
> Subject: RE: [jBoss-Dev] EJB passivation/activation
>
> Marc,
> Not really concerned about passivating a particular
> bean, I just want to set up a situation that will
> passivate ANY bean as opposed to a PARTICULAR bean.
>
> I would imagine most containers use a LRU approach, I
> just want to force passivation/activation and verify
> the callbacks from the container. Each bean will keep
> a rolling history of its own activation/passivation
> which will become part of its state. The client can
> then extract this history and verify that all the
> correct callbacks are being invoked by the container
> on the bean in the correct order.
>
> cheers,
> peter
>
>
> --- marc fleury <[EMAIL PROTECTED]> wrote:
> >
> >
> > > -----Original Message-----
> > > From: [EMAIL PROTECTED]
> > > [mailto:[EMAIL PROTECTED]]On Behalf
> > Of Peter Braswell
> > > Sent: Wednesday, June 28, 2000 2:43 PM
> > > To: jBoss Developer
> > > Subject: [jBoss-Dev] EJB passivation/activation
> > >
> > >
> > > All,
> > > Whats the best way to force these to occur give
> > the
> > > current construct of jboss?
> > >
> > > I suspect its to monkey around with the jboss xml
> > file
> > > to specify minimum and maximum instances and in
> > the
> > > client create a number of connections greater than
> > the
> > > minimum specified in the xml. Am I on the right
> > > track?
> > >
> > > Essentially I want a scheme to force activation
> > and
> > > passivation.... :-)
> >
> > The plugin we have with AC is the random passivation
> > one. I am not sure it
> > is controllable.
> >
> > marc
> >
> > >
> > > cheers,
> > > the JCTS guy (aka Peter)
> > >
> > > __________________________________________________
> > > Do You Yahoo!?
> > > Get Yahoo! Mail - Free email you can access from
> > anywhere!
> > > http://mail.yahoo.com/
> > >
> > >
> >
> >
>
>
> __________________________________________________
> Do You Yahoo!?
> Get Yahoo! Mail - Free email you can access from anywhere!
> http://mail.yahoo.com/
______________________________________________
FREE Personalized Email at Mail.com
Sign up at http://www.mail.com/?sr=signup
