Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: EE-3.3.0.GA, 4.0.BETA, 4.0
-
Component/s: ICE-Components
-
Labels:None
-
Environment:Compat components
-
Assignee Priority:P1
-
ICEsoft Forum Reference:
Description
Similarly to ICE-9348, but involving the compat components.
As reported in the forum, this renderer uses instance fields that they read from and write to during rendering:
- SelectInputTextRenderer
Additionally, auditing found a problem with:
- OutputStyleRenderer
Renderers are application scoped, and can be used simultaneously by different requests / lifecycles. They should never use instance fields that are written to and then read from during a discrete render, since the same Renderer instance is used across threads for different views and users.
As reported in the forum, this renderer uses instance fields that they read from and write to during rendering:
- SelectInputTextRenderer
Additionally, auditing found a problem with:
- OutputStyleRenderer
Renderers are application scoped, and can be used simultaneously by different requests / lifecycles. They should never use instance fields that are written to and then read from during a discrete render, since the same Renderer instance is used across threads for different views and users.
Only these two were actually broken:
icefaces3/compat/components/src/main/java/com/icesoft/faces/component/style/OutputStyleRenderer.java
browserSpecificFilename
/Users/mark/Documents/ICEsoft/trunk/icefaces3/compat/components/src/main/java/com/icesoft/faces/component/selectinputtext/SelectInputTextRenderer.java
domUpdateMap
The rest were ones that were alright but failed the stringent test set by
ICE-9358.icefaces3 trunk
Subversion 36235
icefaces EE 3.3 branch tag
Subversion 36240