This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
<jsp:scriptlet> should be treated the same way as <% is in jsp and tag files and </jsp:scriptlet> should be treated the same way as %>. The bodies of <jsp:scriptlet> tags are not being treated as java but should be. There is no syntax highlighting or code completion in the <jsp:scriptlet> and <jsp:declaration> tags. This is a bug.
This is definitely a bug for JSP Documents (JSP page in form of a XML document), but I am not sure if it applies for JSP page itself (not in xml format). Since we are very close to the end of the nb3.6 FCS we cannot fix this in 3.6 ritgh now => setting target milestone to Promo-D (nb4.0).
There is not enough time for the implementing this feature.
Most of the users use standart syntax for writing jsps. Jsp documents are more often generated by tools than written by hand so the need of code completion and coloring is controversial. Moreover fixing this would require making lot of potentially dangerous changes in many jsp editor areas. Setting TM to future.
Come on, 4.1 is supposed to be a J2EE IDE, so it should support syntax highlighting for all J2EE code, especially when the logic in the IDE already exists and it is just a question of getting it to recognize three more tags. When you have jspx files generated on the fly be another app, it is usefull for debugging purposes, if NetBeans can then display that code with syntax highlighting and offer code completion when you think the embedded java generated is wrong. There should be no controversy on this. There is no need to limit the scope of NetBeans so much.
Reverting Version/TM setting. We will discuss bug fix impact and rethink its defect/feature status.
Changing this issue type to FEATURE. There has never been a support for this. Please comment if you do not agree.
*** This issue has been marked as a duplicate of 46000 ***