If your methods are public/package methods but do not have component interfaces available, then these methods are not executed directly by the container. they're either called by other container initiated methods, or outside the container. if it's the former, then make a test for the method which does call your method. cactus is for testing components managed by the container and specifically the methods the container calls on those components. anything more fine grained and it doesn't make sense to run the tests in the context of a container.
> -----Original Message----- > From: Ron Roth [mailto:[EMAIL PROTECTED] > Sent: Monday, May 10, 2004 10:06 AM > To: Cactus Users List > Subject: RE: EJB testing > > > So it's a tradeoff of testing in container vs. testing > non-interface methods? Is there any way to have both? > > Ron > > -----Original Message----- > From: J. B. Rainsberger [mailto:[EMAIL PROTECTED] > Sent: May 7, 2004 5:53 PM > To: Cactus Users List > Subject: Re: EJB testing > > > Ron Roth wrote: > > > Hi, > > I want to test methods in an EJB that are not part of the > local/remote interface. Is it possible to do this? > > Instantiate the EJB implementation class in a plain old JVM > then invoke > the methods. Voila. > -- > J. B. Rainsberger, > Diaspar Software Services > http://www.diasparsoftware.com :: +1 416 791-8603 > Let's write software that people understand > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
