[Arnoud Martens]

I have found out that imports for new classes are automatically added in the JSP editor. That is good for new developments.

Looking at a massive project with too many and general imports (using wildcards) in the JSP’s I am really missing the ability to Organize the imports for existing files similar to the feature in the Java Editor. Even more so because the compiler does warn about unused imports.

Hopefully something worth considering.

[beasys]

I vote for that feature also – I have * imports all over the place in my jsps and it’ll be nice to organize them. However I understand the complexity of doing that – because when you are editing an jsp which is statically included by some other jsp, what does organize imports mean – do we want to duplicate the same imports in the parent or the organize imports is smart enough to find out and add only the imports that are actually needed ?

— Jalpesh.

[No Operation]

Have you considered include files? Lets regards the usage of a JSP fragment import.jsf:

<%@page import="java.util.Map"%>
<%@page import="java.util.List"%>

And some JSP file who uses that fragment some.jsp, and contains scriptlets:

<%@ include page="import.jsf" %>
<% // some code
%>

I assume that the organize feature should always only affect the jsp file, never fragments, because this could and will have mage side effects.

NOP

[Riyad Kalla]

NOP you should have your tagline changed from “Registered Memeber” to “Good Design Consultant”, or atleast at it to your sign 😀

[Author]

Posts