| Summary: | Symbols resolved as properties behave differently than when same is resolved as built-in variable | ||
|---|---|---|---|
| Product: | [WebTools] Java Server Faces | Reporter: | Gerry Kessler <gerry.kessler> |
| Component: | JSF Tools | Assignee: | jsf inbox <jsf-inbox> |
| Status: | NEW --- | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | raghunathan.srinivasan |
| Version: | 3.2 | ||
| Target Milestone: | Future | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
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. }