Raj, Cactus/JUnit's philosophy is to assure that each test method executes independently...So it is not surprising that a new bean is created each time. However, there are ways to get around this when you need global setup, etc. I'm a little unfamiliar with stateful session beans. Perhaps you can give a simple case of what you'd like to accomplish in some detail and we can assist you...
Cheers, Nick -----Original Message----- From: Raj Govindarajan [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 31, 2001 6:19 AM To: [EMAIL PROTECTED] Subject: Testing Stateful Session Beans with Cactus Hi All, I am trying to use Cactus to test EJB's. I am encountering a problem while trying to test a Stateful Session Bean. It seems to me that Cactus is looking up and creating the Bean for a every test method in the Test class. Because of this, I could not test whether the Bean maintains state between requests. Am I right about this, does Cactus work this way. If yes, are there any workarounds for this problem. Kindly let me know. Note : I had written the getting context and lookup code in the setUp() method. Thanks for your time, Raj -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
