| jsp's are re-compiled after every tomcat restart? [message #88894] |
Tue, 29 May 2007 14:31  |
Eclipse User |
|
|
|
Hi Simon,
as you know :), I'm running Equinox with Tomcat 5.5, and i noticed that
whenever I start my Tomcat, the compiled jsp's in my Tomcat working
directory are always deleted on startup and compiled again, when they got
loaded.
Is there a way to configure my HttpService or HttpContext, that my cached
(compiled) jsp's become reusable (Tomcat default behaviour)??
thx,
teos
|
|
|
|
|
| Re: jsp's are re-compiled after every tomcat restart? [message #89133 is a reply to message #88926] |
Thu, 31 May 2007 21:54  |
| Eclipse User |
|
|
|
"teos" <sasa.teofanovic@gmx.at> wrote in message
news:8b28fa3c4b8d9f587da98d2d407efceb$1@www.eclipse.org...
> Yeah, such an option would be nice in a future release :) A last question
> to this topic - when I have compiled jsp's from a last tomcat run in my
> work-dir and I restart tomcat with changed bundles (dependencies), than
> there shouldn't be any references to the compiled jsp's - in this case, I
> could update my eclipse directory (before tomcat start) in the work-dir
> and the already compiled jsp's could be reused - is that so, if they're
> not removed automatically by the framework launcher??
Hmm... I think you're asking about the lifecycle of the work-dir. Keep in
mind that each HttpContext is associated with its own context.temp.dir.
The intent is that your compiled JSPs should be removed along with this temp
dir whenever the associate HttpContext is no longer referenced by a servlet
or resource registration. This might occur if your bundle's dependencies are
changed however the most common case would be if the framework is shutdown.
In addition to regular lifecycle cleanup, to ensure everything from a
previous run was cleaned up properly the HttpService initialization code
will also remove any old HttpContext temp dirs that remain.
>
> thx,
> teos
>
|
|
|
Powered by
FUDForum. Page generated in 0.04195 seconds
Home