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.

Bug 202551 - [71cat] unknown property false errors on map objects
Summary: [71cat] unknown property false errors on map objects
Alias: None
Product: javaee
Classification: Unclassified
Component: Expression Language (show other bugs)
Version: 7.1
Hardware: All All
: P3 normal (vote)
Assignee: Martin Fousek
Depends on:
Reported: 2011-09-23 11:00 UTC by muellermi
Modified: 2013-07-09 13:47 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description muellermi 2011-09-23 11:00:20 UTC
Product Version = NetBeans IDE Dev (Build 201109180600)
Operating System = Windows XP version 5.1 running on x86
Java; VM; Vendor = 1.7.0
Runtime = Java HotSpot(TM) Client VM 21.0-b17

It's a great help to get warnings about unknown properties. But, if something isn't a property, and might been recognized not being one, you'll get a misleading hint:

    public Map<String, String> getPages() {

JSF Page:
            <h:link value="#{msg.lblSummary}"  outcome="#{}"/>
"unknown property page"
This is a usefull warning, cause ther is no such property

            <h:link value="#{msg.lblSummary}"  outcome="#{sessionTools.pages.MainApp}"/>
"unknown property MainApp"
This is an annoying hint. In this case pages.MainApp is a valid expression to retrieve a value of the map.
Switching off these hints is no option, cause I want to get hints about false expressions.
NB should invstigate and recognize "pages" as Map (same for List, ...) and treat "MainApp" as key. Thus, no warning will be displayed.
Comment 1 Marek Fukala 2011-09-26 12:57:24 UTC
valid issue, thanks for the report.
Comment 2 Martin Fousek 2013-07-09 13:47:49 UTC
Fixed as a side effect of changes for the EL3.0 operators. Thanks Muellermi for reporting. Your issue should be gone for sure in dev builds and probably already in the NB7.3.1.

Fixed by web-main #745fb832ac6f.