Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Equinox » reuse of pre-compiled jsp's
reuse of pre-compiled jsp's [message #105849] Tue, 04 March 2008 13:22 Go to next message
Sasa Teofanovic is currently offline Sasa TeofanovicFriend
Messages: 12
Registered: July 2009
Junior Member
Hi,

is there any way to change the deployment configuration for the framework
launcher (server side), so that temporary created context directories
(used for compiled jsp's -> "proxytemp/hc_<hashcode of httpcontext>") are
NOT deleted on startup/shutdown. The problem is, that whenever my web
container (Tomcat) gets restarted - could also be a VM crash in connection
with a watchdog - all pre-compiled jsp's are removed by the framework ->
performance issue!
It would be nice to change that behaviour of 'on-the-fly' jsp-compiling
(perhaps externally) - as I found out, the only way to avoid this, is to
change the implementation of 'ProxyContext' in bundle
'org.eclipse.equinox.http.servlet'!? What could be an alternative
solution, so that already compiled jsp's become reusable (Tomcat default
behaviour)?? Besides, I'm aware that these context directories are removed
in terms of changing dependencies between bundles, however in my
environment, there are no bundle structure manipulations or redeploys
while the web container is running!

thanks in advance,
-teos
Re: reuse of pre-compiled jsp's [message #105865 is a reply to message #105849] Tue, 04 March 2008 15:20 Go to previous message
Simon Kaegi is currently offline Simon KaegiFriend
Messages: 381
Registered: July 2009
Senior Member
Hi Teos,

For your situation I'd recommend that you precompile your jsps and place the
class files directly in a bundle.
You'd then register them like they were servlets and it should all work.
(sort of similar to the regular jsp precompilation deployment style in
legacy(!) webapps)

With a little work caching jsp comilations between framework restarts seems
doable in static cases as you describe but would require us to look at the
framework state to determine if anything has changed and if we should
trigger a recompile. I'm not currently looking at this but feel free to open
a bug and better still submit any ideas in patches.

-Simon


"teos" <sasa.teofanovic@gmx.at> wrote in message
news:81d67aafca609b8cbcda39db3fa2f4ad$1@www.eclipse.org...
> Hi,
> is there any way to change the deployment configuration for the framework
> launcher (server side), so that temporary created context directories
> (used for compiled jsp's -> "proxytemp/hc_<hashcode of httpcontext>") are
> NOT deleted on startup/shutdown. The problem is, that whenever my web
> container (Tomcat) gets restarted - could also be a VM crash in connection
> with a watchdog - all pre-compiled jsp's are removed by the framework ->
> performance issue! It would be nice to change that behaviour of
> 'on-the-fly' jsp-compiling (perhaps externally) - as I found out, the only
> way to avoid this, is to change the implementation of 'ProxyContext' in
> bundle 'org.eclipse.equinox.http.servlet'!? What could be an alternative
> solution, so that already compiled jsp's become reusable (Tomcat default
> behaviour)?? Besides, I'm aware that these context directories are removed
> in terms of changing dependencies between bundles, however in my
> environment, there are no bundle structure manipulations or redeploys
> while the web container is running!
>
> thanks in advance,
> -teos
>
Previous Topic:Bundle-NativeCode problem
Next Topic:bundles on first startup are always started automatically!?
Goto Forum:
  


Current Time: Tue Oct 19 05:14:02 GMT 2021

Powered by FUDForum. Page generated in 0.02027 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top