|
Re: Showstopper Undeploy Problem??: msg#00293java.jboss.user
Jetty and Tomcat both use Jasper as their JSP engine. This is most likely a problem with Jasper, or some other process on your box cleaning up /tmp. If you are sure that no external process is screwing things up, then one way to avoid this happening would be to precompile your JSPs. This means that you will no longer be deploying any JSPs, but compiled Servlets. Then you will have no temporarily cached class files to worry about. advantages are: - compile-time errors will be caught in development, not production - deploying to a heavily loaded site will not cause multiple concurrent compilations of e.g. index.jsp (patch submitted to Jasper) - dispatch of request to servlet is simpler and therefore quicker since it goes direct from Jetty->Servlet and not Jetty-.Jasper->Servlet. - no compile environment needed on your production box - where it may be considered a security hazard. This FAQ contains an entry on JSP precompilation which I hope will be enlightening.... http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/jboss/contrib/jetty/FAQ?rev=HEAD&content-type=text/vnd.viewcvs-markup Jules Frank Morton wrote: Jboss 3.0.0 ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Oh, it's good to be a geek. http://thinkgeek.com/sf
|
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | topic service within an ear, Julien Viet |
|---|---|
| Next by Date: | Re: delayed database inserts., Dain Sundstrom |
| Previous by Thread: | Showstopper Undeploy Problem??, Frank Morton |
| Next by Thread: | Re: Showstopper Undeploy Problem??, Frank Morton |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |