- This topic has 4 replies, 4 voices, and was last updated 20 years, 3 months ago by
.
-
Posts
-
Is there a way to deploy pre-compiled versions of the JSP’s? If so, how do I do it? If not, I would like to make this a feature request for a future version.
1) No there is not currently support for it
2) We can’t add support for it because your app server controls how the JSP page is compiled. If we did deploy precompiled JSPs its entirely possible that an app server’s impl would differ enough that the page would not work on that app server.However, I know for Tomcat and likely other App Servers, there are Ant tasks you can setup to precompile a webapp, that might be somethign you want to look into.
Since in many App Servers, there are Ant tasks that can be setup, and these Ant tasks typically rely on specific Ant libraries that are contained in the installation of the particular App Server – which is all known to MyEclipse (both the App Server and the installation path) – wouldn’t it still be possible for MyEclipse to handle this? Either through Eclipse’s Ant build features, or some other way? I think the point here is that it would be nice if MyEclipse took the time to build the knowledge of how to pre-compile the JSPs in the various app servers, so that we customers don’t necessarily need to do that!
Just a thought …
bdruth,
While this might be a nice feature, we have to way how many resources it will take to support application server version-specific JSP compilation for over 20 servers. Also, remember that each server uses its own compiler that generates JSP’s on its own set of base classes. So, if you’re deploying to both Tomcat and WebLogic what does deploying a precompiled JSP mean? We’d still have to compile server-specific versions for each then deploy them. It seems much more straightforward to just allow the server to compile them the way they want since even if we did it, there’s no time savings since we’d need to do mutlipe server-specific versions.
Scott,
One of the reasons JSPs are deployed ‘pre-compiled’ is so that the server doesn’t need to expend resources compiling the JSPs, the first time they’re requested (some servers probably compile the JSPs when the application is deployed, but not Tomcat).
I know for our projects, Tomcat’s response time is super-fast when the JSP is compiled, but if it needs to compile it first, the impression the end-user gets is that the server is slow … that’s something that we would like to avoid.
The web-apps I have in Eclipse, outside of MyEclipse, use Tomcat’s Jasper2 Ant task to pre-compile the JSPs … its pretty straightforward. But, I like the features MyEclipse provides and so those projects are all the older projects … and as time allows, we’re converting the projects to MyEclipse web module projects. But, then we lose the ability to pre-compile, if we want to use MyEclipse’s deployment features.
I totally understand that you need to weigh what features you want to expend resources on, I just wanted to note that it would be a technical possibility well within MyEclipse’s capabilities, in contrast to a previous comment which appeared to indicate that it wouldn’t be possible.
