Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 312680 - Symbols resolved as properties behave differently than when same is resolved as built-in variable
Summary: Symbols resolved as properties behave differently than when same is resolved ...
Status: NEW
Alias: None
Product: Java Server Faces
Classification: WebTools
Component: JSF Tools (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: Future   Edit
Assignee: jsf inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-12 14:21 EDT by Gerry Kessler CLA
Modified: 2010-05-21 13:09 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Gerry Kessler CLA 2010-05-12 14:21:00 EDT 
The "implicit" scoped variables (applicationScope, sessionScope, etc.) will provide resolved maps of properties.   However, the same is not true when the scope maps are provided as properties.

ex.   sessionScope == facesContext.externalContext.sessionMap

Content assist for #{sessionScope. } will yield all session scoped managed beans.   The same is not true for #{facesContext.externalContext.sessionMap. }