[emmanuel]

Could MyEclipseIde be extended please, to deploy parsed and compiled JSPs into the server’s ‘work’ file system.

This will eliminate the delay, whilst they are being parsed and compiled by the java application server which seems to take much longer than when done via Ant.

[a4dev2]

I’d really like this too, but I think this is pretty application server-specific. Websphere works in a very different way than Tomcat, etc.

[Riyad Kalla]

This is true and also compilers differ slightly from app server to app server. So lets say we deployed something that we compiled to your app server, and it ran fine and then you deployed the app into production, and it crashed with a NullPointerException… its a trade off, but we wanted to take a safer approach.

Also this request, while nice, hasn’t been demanded by more than a few people so we are trying to balance what the majority of people want first. Its a tricky balancing act for us 😉

[emmanuel]

All points taken.

Could we maybe approach it this way? 😮

a) Could the compiling not be app server specific; MyEclipseIde knows which app server it is deploying to?
b) What are the chances that we could run a poll related to this feature request?

Kind regards
Emmanuel

[Riyad Kalla]

a) THat’s a good question, let me run this by Michael.
b) Definately, I believe any user can start a poll (when you post a new topic in the forum). If you can’t, let me know and I’ll start it.

[support-michael]

Thanks for the feedback. We discussed this in the early days of ME development and rejected it for a number of reasons. Since I work on the ME platform I share with you some of the discussion points:

0) Typically, precompilation of JSPs is a production concern and there has been very little request for this feature, i.e., a nice to have but not essential for development productivity
1) ME enables a project to be deployed to multiple servers simultaneously. So how to support such configuration (see #2)
2) ME projects are independent of servers or deployment facilities (no coupling), so more project state maintenance is required
3) Interfacing to various JSP compilers and their quirks and the state mgmt concerns has not seemed to be a cost effective feature.
4) ME’s JSP editor is tightly coupled to a proprietary JSP compiler that is customized to support the editor’s requirements. The results it produces are not portable. Because of #3 the JSPs would have to be explicitly compiled prior deployment, possibly during the deployment step. This would be really slow if all you wanted to do is test 1 JSP.

We are definitely interested in user feedback and interests for all features and feature prioritization. But since we lack infinite resources feature tradeoffs have to be made. So is JSP compilation more important than say, JSF or WYSIWIG support? Just curious. 🙂

[emmanuel]

Thank you for the feedback.

BTW., in terms of the question related to JSF or WYSIWIG; I’m biased, those aren’t features I use; so I’ll vote JSP compilation; I suspect a high number of people use it and sit waiting for app server compilations during develop/test.

Thank you again for the feedback, I’ll stick to Ant to deploy compiled JSPs. 🙁

Kind regards
Emmanuel

[Author]

Posts