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.
[ BUILD # : 200710040000 ] [ JDK VERSION : 1.6.0_02 ] I couldn't track down how to reproduce the issue for a long time until I've finally figured it out. It's reproducible, but the step order is important. It happened right after I'd upgraded NB to the latest nightly build. 0/ Define a Java EE server 1/ Create a JSF webapp 2/ Create a managed bean - employee - with some properties 3/ Close NB 4/ Remove NB home repository, i.e. ~/.netbeans 5/ Open NB and the webapp project (there should be a warning message that the appserver's not defined - we'll get back to it soon) 6/ I'm not sure whether it's required or not, but do it just to reproduce the issue - select Run menu from the project context menu. You should see an error that no appserver's defined. 7/ Define an jee appserver and select it for the project 8/ run Clean and Build in the project (I think that's one of the most important step to reproduce the issue as likely some NB internal helper files are gone afterwards from dist/build directories or such) 9/ Open welcomeJSF.jsp file and type in <h:outputText value="#{">. Press Ctrl+Space to open up JSP completion. No managed beans are available. (!) After a while the managed beans from the project are available already.
Sorry, I can't reproduce this. Can you reproduce in the latest daily build? By the way, in step 9, is there any difference if you wait until the Java classpath scan finishes?
Actually, perhaps I found a way to reproduce this while working on another issue. 1. In a JSP file type "<h:outputLink ". 2. Invoke code completion, type "va", press Tab. The IDE completes to "value". 3. Type '="#{' (without the apostrophes. The code completion comes up with the managed bean missing.
moving opened issues from TM <= 6.1 to TM=Dev
The code completion for the managed beans is now more robust and I no longer see this issue.