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/
