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.
This is an umbrella issue for the set of Code Completion issues related to JSP pages in XML syntax ("JSP Documents"). See Show Dependency Tree to identify the real issues, please make any new Code Completion issues related to JSP Documents block this issue.
This will be done in the future.
If you are going to say NetBeans 4.1 supports J2EE 1.4, add support for <jsp:scriptlet>, <jsp:declaration>, <jsp:expression>. When a page is loaded, just add <![CDATA[ // <% after each opening tag and add // %> ]]> before each closing tag. If it is really so hard to make these three tags be recognized by NetBeans, just add that above workaround automatically each time a jspx page is opened. You could even go as far as to dynamically add the work around when a page is opened and dynamically remove the work around when a page is saved. Thus, the user gets clean syntax highlighting and code completion without any extra effort. Even if they don't author any jspx files, this can come in handy when debugging applications that generate jspx files on the fly.
It's not so hard to do this. Thanks for the input, but I'm afraid we are not able to do it for NB 4.1 We are after feature freeze. It's good enhancement for the next release. It's better to create separate issue and link the new issue with this issue.
Reverting Version change.
Most of the dependent issue of this umbrella one can be solved by the new editor infrastructure we are likely going to adopt in 6.0.
Just a comment - the dependency tree is weird. This umbrella issue cover all those dependt ones, but the 80805 is an issue which blocks all of them. The dependency direction should be probably changed for the 4***** issues and this one. It can be confusing now.
moving opened issues from TM <= 6.1 to TM=Dev
This bug was reported against NetBeans IDE 6.0 or an older release, or against a non-maintained module. NetBeans team does not have enough resources to get to this issue, therefore we are closing the issue as a WONTFIX. If you are interested in providing a patch for this bug, please see our NetFIX guidelines for how to proceed. We apologize for any inconvenience. Thank you. The NetBeans Team