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.
Variables declared inside JSP declarations like <%! private int access_count = 0; %> needs to be parsed and offered to user when she/he writes scriplets.
This problem is little more generic. If the JSP page containg more scriptlets the CC goes throught these scriptlets and does not offer elements from another scriptlets event though it is logic to offer CC above whole JSP page.
Target milestone -> 3.3
Change of e-mail address
*** Issue 14915 has been marked as a duplicate of this issue. ***
Target milestone -> 3.3.1.
*** Issue 24408 has been marked as a duplicate of this issue. ***
Set target milestone to TBD
*** Issue 25401 has been marked as a duplicate of this issue. ***
*** Issue 32517 has been marked as a duplicate of this issue. ***
how has this problem been pushed back so many times (years)? This is still occuring in the 3.5 release, and it seems just as many people are still noticing it. Was the change so big that it really required to be pushed back indefinately? (I honestly don't know, it could be a huge change). I vote for this.
Also, this is standard functionality of all other IDEs, I'm not entirely convinced this is an enhancement request, as it is a request for the IDE to behave onpar with all other IDEs. Also, consider the example: <% String s = "Hello"; %> <HTML> <BODY> <%= s.| %> </BODY> I do not get any code completion for the s variable... while this variable is in scope, it technically should be auto completed, as Netbeans offers autocompletion for it while its inside of the first block, which is also in scope. While this may not throw any exceptions, I do see it as a defect in the scoping of the variables (I don't mean to throw out random verbs, I don't know how variable scope and autocompletion is determined, but it seems near- sighted currently :) </HTML>
Riyad: you are right the problem is pretty old but all the time we have to balance our work between different areas. One possible reasoning for assigning such a low priority is that scriplets in JSP are not so prefered solution when you use MVC pattern ;-) OK, I understand you and admit that we postponed this when we expected that the editor will be substantially reworked due to changes in base editor (lexer and other changes). Petr, I think the latest jspparser should help with this problem.
Radim, Ok I can see your point and definately understand you guys have a lot of other work to do. I really need to read a good Model2/MVC book, because I've got scriplets all over the place, and they are killing me :)
*** Issue 30312 has been marked as a duplicate of this issue. ***
It works fine in NetBeans 4.0 Marking as Fixed.