According to your bug 44739, to be unable to change a file extension in NetBeans IDE is not a real problem. Well, maybe they use too often Microsoft Windows with the "hide known extensions" innovation activated. Unfortunately the problem exists for real. If you include a jsp fragment through <jsp:include>, you are advised to use the "jspf" extension. Now, if you include something with <%@include%>, there is no standard extension, and no, using "jspf" is not a good idea, because those two types of inclusion are two really different things. Imagine for now that your design changes for the static include to dynamic include... Leave aside NetBeans, change the file extension, come back to NetBeans, wait for the files tree to be refreshed, and trigger a clean build. Do you see a usability problem ? All I read is "Won't fix".