Hi Rao, It depends... ;-)
Cactus will use the container you intend to deploy on, thus performing "real" integration tests. If you use openEJB for testing code that is supposed to be deployed on WebLogic, then you'll also need to run some additional tests on WebLogic to ensure it really works (I would if I were you). I don't see Cactus and openEJB on the same level. Cactus integrates several containers to run integration unit tests on (the Cactus framework does support running on openEJB). However, ATM, the Cactus front ends (i.e. the <cactus> Ant tasks and the Maven plugin) do not yet support openEJB (just because we haven't done it). It's part of our todo. For now, you'll have to start openEJB manually if you wish to run Cactus tests on openEJB. In the future the Cactus project would really like to add an openEJB integration in the same way as Cactus already has a Jetty integration (embedded usage of the container). Thanks -Vincent > -----Original Message----- > From: nojeal [mailto:[EMAIL PROTECTED] > Sent: 23 June 2004 08:02 > To: [EMAIL PROTECTED] > Subject: [openejb-user] OpenEJB vs Cactus > > hi, > We are trying to analyze which is better framework to > test EJB spec 2.0. > 1) openEJB > 2) cactus. > > openEJB documentation says it only supports EJB spec > 1.1, so can I or not test message driven beans using > openEJB. Also, I would like to know you guys opinion > on using cactus to test EJBS > > Thanks, > rao > > ===== > love ever, hate never > > > > __________________________________ > Do you Yahoo!? > New and Improved Yahoo! Mail - Send 10MB messages! > http://promotions.yahoo.com/new_mail
