- This topic has 4 replies, 4 voices, and was last updated 20 years, 10 months ago by
.
-
Posts
-
Hi,
Is it possible to use the JSP 2.0 EL tags and JSTL 1.1 using the MyEclipse 3.7.2 version?
I am currently using the JBoss 3.2.5 + TC5 which support JSP 2.0 but I don’t make use of them and still using the JSP 1.2. I am working with Struts 1.1 + JSTL 1.0.
What steps do I need to take in order to make use of JSP 2.0 and JSTL 1.1 in my project under MyEclise 3.7.2?
Thanks in advance,
Erez
AFAIK MyEclipse unfortunately does not support JSP 2 (nor JSTL 1.1) yet.
On the roadmap for MyEclipse 2.8 there is a “JSP 2.0 preview”, although I’m not sure what is meant.
Erez,
ME does not support JSP 2.0 yet, but you can use JSTL just like any other taglibs (Struts, WebWork, etc.). While you won’t get autocomplete in the EL sections, MyEclipse will ignore them so you can still use EL without getting error markers.I’ve done some simple JSTL pages before in ME and they worked fine.
Hi,
@support-rkalla wrote:
Erez,
ME does not support JSP 2.0 yet, but you can use JSTL just like any other taglibs (Struts, WebWork, etc.). While you won’t get autocomplete in the EL sections, MyEclipse will ignore them so you can still use EL without getting error markers.I’ve done some simple JSTL pages before in ME and they worked fine.
I’ve spent some time on this topic last night. After createing a Servlet 2.4/JSP 2.0 compatible (foundation of an) application during the last few days i had some mysterious problems related to JSTL/JSP2.0 JSP files.
MyEclipse soaked all available CPU cycles for a couple of seconds (60 – 70) while trying to rebuild the workspace. This failed (with some error related to the BJE JSP builder) and an OutOfMemory afterwards. Sometimes instead of that OutOfMemory Exception Eclipse showed an “Resynchronizing Tables” for anonther minute or so.
As a workaround i disabled the BJE Jsp Builder and since then everything works again as expected (no more MyEclipse Lock Up).
This never happened in my projects based on Servlet 2.3 / JSP 1.2 / JSTL 1.0 .
It’s directly related to the use of Servlet 2.4 / JSP 2.0 / JSTL 1.1 .
But as long a an usable workaround is available….
Sincerly
Ralf this is strange, can you email a small project that exhibits this behavior to support@genuitec.com with a reference to this thread? It could prove to be very helpful for the devs to have it as reference.
