Jeffrey,
After looking more closely at the scripts you
provided I noticed that you copied the test war file to the location where
JBoss/Tomcat is installed. This is fine but I have been trying to follow a
different approach so far with all other scripts for other containers (I'm not
sure it is a correct approach either ... !). I have always configured the
servlet engines so that the test webapp would execute in it's own directory
(named out in the cactus sample) so that :
- it would not interfere with other applications
that might be installed in the servlet engine,
- it is a bit faster as the servlet engine does not
have to load/setup the other webapps,
- we can have dedicated servlet engine
configuration files for the test,
- do not "pollute" the servlet engine with test
webapps
So far, I have found that it was an easy thing to
do as all servlet engine give you the freedom to configure where you put the
webapps.
If you have some time, would you be able to help me
rewrite the 'prepare_tests_jboss_221' target to work
this way ? (You can check how it works on Tomcat 3.2 to understand better what I
meant above) ?
Thanks a lot.
Vincent.
|
Title: [cactus] Using Cactus with JBoss-2.2.1 with Embedded Tomcat
- [cactus] Using Cactus with JBoss-2.2.1 with Embedded Tomc... Jeffrey Madynski
- Re: [cactus] Using Cactus with JBoss-2.2.1 with Embe... Vincent Massol
- Re: [cactus] Using Cactus with JBoss-2.2.1 with Embe... Vincent Massol