Return-Path: Delivered-To: apmail-jakarta-cactus-user-archive@apache.org Received: (qmail 54125 invoked from network); 21 May 2002 23:01:49 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 21 May 2002 23:01:49 -0000 Received: (qmail 1773 invoked by uid 97); 21 May 2002 23:01:54 -0000 Delivered-To: qmlist-jakarta-archive-cactus-user@jakarta.apache.org Received: (qmail 1757 invoked by uid 97); 21 May 2002 23:01:53 -0000 Mailing-List: contact cactus-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Cactus Users List" Reply-To: "Cactus Users List" Delivered-To: mailing list cactus-user@jakarta.apache.org Received: (qmail 1745 invoked by uid 98); 21 May 2002 23:01:52 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) From: "Nicholas Lesiecki" To: "Cactus Users List" Subject: RE: dual in/out container testing? Date: Tue, 21 May 2002 16:09:43 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <007101c2010e$df6eddb0$a5c8c8c8@octovma> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Yep, sorry I didn't post the link earlier, it's been an exciting weekend. Nicholas Lesiecki Principal Software Engineer eBlox, Inc. (520) 615-9345 x104 Check out my new book!: Java Tools for Extreme Programming: Mastering Open Source Tools, including Ant, JUnit, and Cactus http://www.amazon.com/exec/obidos/ASIN/047120708X/ Check out my articles on AspectJ: Test flexibly with AspectJ and mock objects: http://www-106.ibm.com/developerworks/java/library/j-aspectj2/?loc=j Introduction to AspectJ http://www-106.ibm.com/developerworks/library/j-aspectj/index.htmlloc=dwmain -----Original Message----- From: Vincent Massol [mailto:vmassol@octo.com] Sent: Tuesday, May 21, 2002 2:31 PM To: 'Cactus Users List' Subject: RE: dual in/out container testing? ... and the article is available at http://www-106.ibm.com/developerworks/java/library/j-aspectj2/?loc=j and has been added to the Cactus web site in the news and resource web pages. Thanks Nick! -Vincent > -----Original Message----- > From: Nicholas Lesiecki [mailto:nick@eblox.com] > Sent: 09 May 2002 21:43 > To: Cactus Users List > Subject: RE: dual in/out container testing? > > I actually did exactly this for a forthcoming article on IBM's > developerworks. I used AspectJ (www.aspectj.org) to change the test case's > parent class depending on which deployment I was running. Cool stuff. I'll > be sure to post a link to the article here as soon as it's published. > > Cheers, > > > Nicholas Lesiecki > Principal Software Engineer > eBlox, Inc. > (520) 615-9345 x104 > Check out my new book!: > Java Tools for Extreme Programming: Mastering Open Source Tools, including > Ant, JUnit, and Cactus > > http://www.amazon.com/exec/obidos/ASIN/047120708X/ > > Check out my article on AspectJ: > http://www-106.ibm.com/developerworks/library/j- > aspectj/index.htmlloc=dwmain > > > -----Original Message----- > From: Mike Wyszinski [mailto:mike_wyszinski@yahoo.com] > Sent: Wednesday, May 08, 2002 4:19 PM > To: cactus-user@jakarta.apache.org > Subject: dual in/out container testing? > > > OK, > > Is it possible for cactus tests to be run as > standalone plain old junit tests? > > Here's our situation: > > 1)We are writting some "Foundation" SessionEJBs > 2)We using Sun J2EE Business Delegate pattern to > isolate clients from our deployment architecture > Therefore, we can run the same logic/code from within > a EJB environment or not. > 2)we chose to write POJT (plain old junit tests) to > test the basic logic AND use cactus to test > in-container reaction to our code. > > Well doing it that way has meant us having to copy n' > paste the same test logic into 2 classes: > > 1)public class XTest extends TestCase > 2)public class XCactus extends ServletTestCase > > We'd like to get rid of the duplication effort, any > ideas on how to centralize the test code and have it > runnable as ServletTestCase And TestCase? > > BTW we thought about using composition ie: > public class XTestLogic{ > //all test code in here > } > public class XTest extends TestCase { > private XTestLogic testlogic = new XTestLogic() > } > public class XCactus extends ServletTestCase{ > private XTestLogic testlogic = new XTestLogic() > } > > but all the assertX() are obviously not available in > XTestLogic. > > any insight would be appreciated, > Mike > > __________________________________________________ > Do You Yahoo!? > Yahoo! Shopping - Mother's Day is May 12th! > http://shopping.yahoo.com > > -- > To unsubscribe, e-mail: > > For additional commands, e-mail: > > > > -- > To unsubscribe, e-mail: unsubscribe@jakarta.apache.org> > For additional commands, e-mail: help@jakarta.apache.org> -- To unsubscribe, e-mail: For additional commands, e-mail: -- To unsubscribe, e-mail: For additional commands, e-mail: