- This topic has 2 replies, 2 voices, and was last updated 20 years, 8 months ago by
.
-
Posts
-
This feature may in fact be already available but if not a feature that includes precompiled JSP classes in the deployment would be very handy.
Robert
Unfortunately, I think, it is problematic. The generated JSP code and what other classes it uses (and also the classnames of the generated servlets) varies from server to server. Therefore to be able to precompile JSP files for a server, you need to have that server installed on the developer machine.
So far it was not necessary to have the server installed on your machine to be able to develop with MyEclipse.
Therefore it might be good to have it as an optional feature, but it definitely should not be something which is forced on the user.
Just my 2cents…
Regards,
Robert Varga
You’re right, I certainly wouldn’t advocate such a feature as mandatory and no doubt there will be significant differences between application servers.
My experience is limited to Tomcat (embedded in JBoss and Sun ONE app servers) and for JBoss in particular it’s a relatively simple process to add a couple of extra Ant tasks to precompile the JSPs and add them to the deployment – whether JBoss is local or remote.
I guess I would characterise it as a ‘nice to have’ rather than a ‘need to have’ feature, but with all of the other miracles being acheived in MyEclipse, it’s one I would still like to see as an option – even if it’s only for the app servers it proves not to be problematic for.
Robert
