Hello, all.
My env:
jboss-3.0.3_tomcat-4.1.12
Sun JDK 1.4.1_01
Linux 2.4.19-16mdk, Mandrake 9.0, i686
Apache 2.0.43 w/JK2.0.2->Coyote
When I was using jboss-3.0.3_tomcat-4.1.12, undeployment of my app
caused a stack trace in the jboss server console. That seems to be
fixed in jboss-3.0.4_tomcat-4.1.12, BUT I"ve got a new problem: The
undeploy blows away my tomcat work directory!
To be more specific, actions of redeploy/undeploy/shutdown all make this
directory:
/opt/jboss/tomcat-4.1.x/work/MainEngine/localhost/MyAppDir
get blown away.
The side effect of this means that whenever I re(hot)deploy my app, all
my JSPs have to recompile all over again, even if they haven't changed.
This absolutely kills iterative development by increasing
redeployment/retest time drastically.
Is there someway I can disable this behavior? I've used JBoss for a
LONG time (many versions of it), and this is the first version I've seen
that blows away the web container's already-compiled JSPs. I'm just
fine with this happening on a production server - but not when I'm
trying to develop.
I haven't seen if this happens with the latest Jetty bundle, but I'm
guessing it does... See the very recent email on this list by Todd Benge
"Change Jetty Deployment Dir" - he says "...and also instruct Jetty not
to clean the directory on undeployment?"
Thanks for any and all help,
David
---------------------
David Ward
[EMAIL PROTECTED]
http://www.dotech.com
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
