Laurent, Thanks again. This is useful information which you confirm and I see why now and that is what I was trying to confirm or deny.
... >All the tests cases go on both client and server. If I understand >correclty, >all beginXXXX() and endXXX() methods are executed on the client and the >testXXX() methods are executed on the server. > > > Ok, here is what I mean. For a simple servlet redirector test case, say > > TestCase1, what would be the structure on the client and on the server? > > > >Both. > > >It's necessary because you can't put the beginXXX() and endXXX() methods in >a separate calss. > > >Anything that extends ServletTestCase or JspTestCase or FilterTestCase goes >in > there. If you're only extending TestCase, you don't need to put the >classes > in the web app (because most likely, you aren't testing any J2EE stuff). You mention that "Now if you say your client and your server are different, I don't think Cactus s what you're after. I could be wrong, don't take my word for it. It really depends on what you're trying to test. If you're trying to test methods from your J2EE objects, then Cactus is your friend. " Yes, actually want I want to test are EJBs running in the EJB container and do so from a servlet running in the Web container, all in the same VM (specific version of a specific VM) and do so from a client running somewhere in another VM (any vendor VM) using straight HTTP to send requests tot the test cases. There are no user interface considerations at all, so it would seem, HTTPUnit is not what I want, and Cactus is. So, from what you are saying I need to be putting the test case code in both the client and the Webapp (itself a "client" to the EJB). >-- >Laurent Duperval <mailto:[EMAIL PROTECTED]> _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
