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.
Created attachment 103185 [details] incorrect autocomplete options Managed bean names are not parsed, or are not presented as an option in the autocomplete menu. For example: @ManageBean(name = "beanName") public class MyBean {... instead of showing 'beanName' in the autocomplete menu, 'myBean' is presented. If I choose the provided option, I can no longer access the properties of the chosen bean by using the '.' operator; i.e. if I now press Ctrl+Space, a list of manged beans names (formed by the class name of the bean), scoped objects and expression language operation keywords is presented. If I however manually type the name of the bean, in this example 'beanName', than the options are available.
reproducible, regression of the el redesign
fixed in web-main#c99301c7d7a5
Integrated into 'main-golden', will be available in build *201011250001* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main/rev/c99301c7d7a5 User: Marek Fukala <mfukala@netbeans.org> Log: #192279 - Autocomplete in JSF editor doesn't work properly for EL expressions.
Created attachment 103372 [details] Screenshot of the autocomplete not working properly.
I can confirm that the defect described in the report was fixed in the 201011250001 build. However, I noticed some more erroneous behavior of the autocomplete in the xhtml editor. Occasionally, a property of a manged bean is underlined with yellow where the hint says 'Unknown property "propertyName"', although it exists, and was successfully retrieved by the autocomplete functionality; Also, the autocomplete does not work for retrieving keys from a bundle file, the behavior is the same as was described in the original bug submission, i.e. on Ctrl+Space instead of the keys of the bundle file, the beans, scoped objects and expression language operation keywords are presented. This happens both in the NB 7 Beta as well as in the 201011250001 build.
Please do not use reopening fixed issues for adding new bugs! I've created a new issue 192527 - JSF Expression Languages issues. I'll look at the problems ASAP.