An alternative approach might be to use the itest plugin. You can see an example of this in the openejb itests module. For openejb, this depends on having a maven plugin to deploy/undeploy applications to openejb, and also start/stop openejb. IIUC the cargo project has somewhat related functionality for some application servers, but I've never looked at it.
Hope this gives you a starting point for something that might be useful,
david jencks
On Feb 28, 2005, at 10:58 AM, Poppe, Troy wrote:
Maybe I'm missing something, but Cactus isn't mentioned in that URL at all.
T
-----Original Message----- From: Ryan Sonnek [mailto:[EMAIL PROTECTED] Sent: Monday, February 28, 2005 1:55 PM To: Maven Users List Subject: RE: Multiproject and Testing EJBs
try this: http://wiki.codehaus.org/maven/CreatingEjbApplications
-----Original Message----- From: Poppe, Troy [mailto:[EMAIL PROTECTED] Sent: Monday, February 28, 2005 12:28 PM To: 'Maven Users List' Subject: Multiproject and Testing EJBs
I've got a multiproject set up that generates an EAR artifact. I'd like to write
some JUnit or Cactus tests to test the EJBs that I have in an EJB-JAR in my
EAR.... I am using JBoss as my deployment environment...
I'm curious if anyone can share their experience setting up JUnit/Cactus tests...
Did you place the tests in the EAR project? Did you create a JBoss config/deploy
directory structure in your project for the automated testing? Any documentation
that might suggest some best practices?
Thanks.
Troy Poppe
--------------------------------------------------------------------- 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]
