I think JBoss employs the lead developer of Tomcat 5.0, so there should be no danger 
there :-)

Regarding replacing Tomcat with Jetty, I did this on our Jboss 3.2.3 setup before 
X-mas. I can't remember the exact details, but it was something along the lines of:

1) Download an older JBoss distribution bundled with Jetty. If you cannot find one on 
the main downloads page, look on the JBoss download page on sourceforge.

2) In your 3.2.5 setup, delete the folder jbossweb-tomcat50.sar

3) Copy across the folder deploy/jboss-x.x.x-jetty-x.x.x.sar from the older JBoss to 
your 3.2.5 deploy folder

4) I had some problems to do with JBoss being compiled with jdk 1.3 and jetty with jdk 
1.4 or something like that. I can't remember exactly what, but in my setup I seem to 
have replaced deploy/jboss-x.x.x-jetty-x.x.x.sar/org.mortbay.jetty.jar with 
org.mortbay.jetty-jdk1.2.jar. A google search for that should help. 

Cheers,

Kab

View the original post : 
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3841233#3841233

Reply to the post : 
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3841233


-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to