[solmyr72]

This message has not been recovered.

[Riyad Kalla]

This message has not been recovered.

[Matthew Pangaro]

How about for use of the new JSP 2.0 prelude feature? I define all of my <%@ taglib …%> definitions in a prelude, so they can automagically be applied to all the JSP files in my application, but the net effect for MyEclipse seems to be that every usage is marked with a warning.

[Riyad Kalla]

Unfortunately this isn’t supported yet, I am going to add a “urgent” flag to this as it’s been filed for a while but got buried under 5.0 work. Maybe we can sneak this into a service release.

[Matthew Pangaro]

Ok, thanks. I guess for now I’ll just get used to the yellow squigglies and no auto-complete.

[Matthew Pangaro]

Any update on this? 5.1 didn’t get JSP 2.0 support, and the roadmap isn’t specific enough to make it clear.

Thanks,
Matt

[Matthew Pangaro]

Anybody out there? Two years later this still hasn’t been addressed. Just curious, thanks.

[Riyad Kalla]

Matt,
Looks like it will be a 6.0 or 6.1 line item, I am personally amazed at how infrequently this has been asked for (which certainly would have bumped the priority) but folks are much more interested in tooling existing apps or support for newer JEE 5 technologies, so those items have been getting our full attention.

I’m really sorry for the wait for the folks that are using the feature though, we never like not covering a feature set that is getting used.

[Matthew Pangaro]

Doh, oh well. It drives me insane because my JSPs have no autocomplete and are filled with error markers. I guess I’ll see how long I can live with that, since it’s not worth putting all that code back into every single JSP file.

Maybe another option would be to add a project-level configuration that says what taglibs, at least, should be available to the JSP editor for all pages, or something like that.

Anyway, thanks for the response.
Matt

[innerlogic2]

I seem to have the same problem. This isn’t even supported?? That’s really bad.

[Matthew Pangaro]

Sooooo….. Now that 5.5 is GA, do you have any idea where this issue is on the project road map? JSP 2.0 is old news and we’re moving on to 2.1 and beyond, and still the basic IDE features aren’t supported if you use the new spec. Any idea on whether this issue is making it into 6.0?

Thanks,
Matt

[Riyad Kalla]

Matt,
The plan is to get all the editors spruced up for the 6.0 release and address issues like this in that release.

[Matthew Pangaro]

Excellent. Looking forward to M1.

Matt

[Author]

Posts