At 11:39 29.6.2000 -0700, you wrote: >JCTS will then need to call "stop->start" on the container... >sure you want to let the client do that? >Driving this from a client is non trivial (hence the wait() trick) Hmm.. I might be missing something quite obvious here but at the risk of sounding stupid I gotta ask... If you guys are doing unit testing, why exactly would you need to get to this type of thing through client and all the layers between it and the container? Why won't you just ask Rickard how the container does the passivation/activation tricks, get a test bean on it, write a unit test that directly hits the container and check that the bean comes back looking alive and all it methods called in the proper order etc etc. Unit test the container, not the bean? me confused...? -- Juha
- [jBoss-Dev] EJB passivation/activation Peter Braswell
- RE: [jBoss-Dev] EJB passivation/activation marc fleury
- Re: [jBoss-Dev] EJB passivation/activation Rickard �berg
- RE: [jBoss-Dev] EJB passivation/activation marc fleury
- RE: [jBoss-Dev] EJB passivation/activation Juha Lindfors
- RE: [jBoss-Dev] EJB passivation/activation Peter Braswell
- RE: [jBoss-Dev] EJB passivation/activation Jeremiah Johnson
- RE: [jBoss-Dev] EJB passivation/activation marc fleury
- RE: [jBoss-Dev] EJB passivation/activation Adi Lev
- RE: [jBoss-Dev] EJB passivation/activation Peter Braswell
- RE: [jBoss-Dev] EJB passivation/activation marc fleury
- Re: [jBoss-Dev] EJB passivation/activation Rickard �berg
- Re: [jBoss-Dev] EJB passivation/activation Andy Abate
- RE: [jBoss-Dev] EJB passivation/activation Peter Braswell
- Re: [jBoss-Dev] EJB passivation/activation Peter Braswell
