Hi Bryce,

> Anyone using the Cactus plugin to test EJBs?

Year works great. I use ServletTestCases to achives it.

> 
> I've setup several different projects. One for persistence 
> classes (CMP
> Beans), one for business classes (Session Beans), etc...

Although I'M a CMP hater I have to maintain a couple of them and so I do
some testcases.
Works fine. 

> 
> I want to use Cactus to perform some integration testing with my
> persistence classes. I'm thinking the best way is to create a seperate
> project just tied to cactus tests for each main project. I think that
> would be easiest, as I could create an ejb-jar for my persistence
> classes, and a war file for my cactus tests that depend on 
> the ejb-jar...

I have a ejb-project which results in a ejb-jar with following project
structure:

project.xml
project.properties
build.properties
|
+- src
   |
   +--java
   |
   +--itest (contains cactus test cases)

the key configuration knowlege is hold in build.properties:

cactus.src.dir=${basedir}/src/itest/
cactus.src.excludes=**/*Mock*      
cactus.home.jboss3x= C:/java/contrib/jboss/jboss-3.2.1_tomcat-4.1.24
cactus.context= jPortal-ejb
         

My project.properties contains the following configuration:

maven.war.webxml=${basedir}/conf/cactus-web.xml

The main step it to deploy the resulting ejb-jar file handy.
In my case this is easy as jboss accepts ejb.jar files and maven supports
jboss deployment. Vincents cool plugin support not every appserver so 


> Anyone who's using Cactus care to comment on their project setup?

I'm very pragmatic in this cases and I don't want to come up with to many
cvs projects.
Please note that cactus:test is halting the VM. This influcenes your build
process when you 
trigger maven to proecess more goals (e.g. 'maven cactus:test'site won't
work).
I don't know if this have side effects on reactor based build (e.g the
multiproject plugin or own reactor builds).

Hope this helps

Bye
Toby

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to