Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 1.7DR#2
-
Fix Version/s: 1.7DR#3
-
Component/s: None
-
Labels:None
-
Environment:ICEfaces
Description
BridgeFacesContext.getELContext() is not currently cached, causing a new instance to be created for each call to the function. The specification indicates that the lifetime of the ELContext should be the same as the FacesContext itself.
The fix is to retain an ELContext instance after the first lazy instantiation.
Issue Links
- blocks
-
ICE-2609 custom ELResolver + custom PropertyResolver
- Closed
Activity
Repository | Revision | Date | User | Message |
ICEsoft Public SVN Repository | #15317 | Fri Dec 07 16:08:33 MST 2007 | ted.goddard | caching ELContext with BridgeFacesContext ( |
Files Changed | ||||
MODIFY
/icefaces/trunk/icefaces/core/src/com/icesoft/faces/context/BridgeFacesContext.java
|
Ted Goddard
created issue -
Ted Goddard
made changes -
Field | Original Value | New Value |
---|---|---|
Status | Open [ 1 ] | Closed [ 6 ] |
Fix Version/s | 1.7DR#3 [ 10112 ] | |
Resolution | Fixed [ 1 ] |
Mark Collette
made changes -
This bug was discovered by the fact that it causes setValue to fail for expressions under Spring Web Flow 2.0 and JSF 1.2.