- This topic has 1 reply, 2 voices, and was last updated 21 years, 5 months ago by Scott Anderson.
-
AuthorPosts
-
casterxMemberJSP Compilation too slow
I am using MyEclipse on a project with about 200 JSPs. During startup or setting changes, the tool proceeds to recompile every page — which is incredibly slow and resource intensive that I get out of memory errors on a 1 gig machine. Is there any way to speed up or make the recompile more efficient?
To get around the problem, I removed the incremental jsp build task, but now, my JSPs don’t get compiled at all. Is there any way to selectively compile individual JSPs to check for syntax error before deployment?
On a side note, is it possible to turn the reload on class change attribute for a deployed context in tomcat?
Thanks…
Scott AndersonParticipantIs there any way to speed up or make the recompile more efficient?
We’re looking into it now for inclusion in a later service release.
To get around the problem, I removed the incremental jsp build task but now, my JSPs don’t get compiled at all.
This was a bad solution. You can simply turn off JSP compilation using the option on the syntax page of the JSP Editor configuration page in the 2.5.1 release.
Is there any way to selectively compile individual JSPs to check for syntax error before deployment?
Yes, turn JSP compilation off while you develop, then turn it back on before deployment. You can either then compile them all, or simply resave the ones you want to recompile and check.
On a side note, is it possible to turn the reload on class change attribute for a deployed context in tomcat?
We’re looking into doing server-specific reloading in an upcoming service release. In the meantime, simply ‘touch’ the web.xml file in your Eclipse project and if you’re using exploded deployment this should indicate to Tomcat to reload the application. More information can be found in the Tomcat documentation.
–Scott
MyEclipse Support -
AuthorPosts