[JAVASERVERFACES_SPEC_PUBLIC-1233] Since 'var' is set by name on the request it is very easy to break. Created: 29/Oct/13  Updated: 01/Aug/14

Status: Open
Project: javaserverfaces-spec-public
Component/s: Components/Renderers
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Minor
Reporter: jid1 Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

IMO, composite components that contain tables or repeats that store variable on the request should be scoped as it very easy to get weird behaviour.
In the context of normal xhtml and includes, it could throw an error saying that the variable has already been defined, if user tries to define it again.

The reason behind the distinction is that you might end up with incompatible 3rd party components when you nest them. In addition, devs should pass the value as an attribute to the composite/custom component.



 Comments   
Comment by Ed Burns [ 01/Aug/14 ]

Set priority to baseline ahead of JSF 2.3 triage. Priorities will be assigned accurately after this exercise.

Comment by Manfred Riem [ 01/Aug/14 ]

Setting priority to Minor

Generated at Tue Mar 28 01:46:52 UTC 2017 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.