Description
The change to CompositeComponentRule committed by MYFACES-2633 actually does break the ezcomp RI sample. Specifically, in the spinner example it is causing the last value submitted to not be updated when you click the reload button. It has reverted to the same behavior that was fixed by MYFACES-2340.
I did some playing around, and it seems that both adding the ValueExpression directly to the map AND calling instance.setValueExpression() seems to resolve both cases.
((UIComponent) instance).getAttributes().put(_name, _attr.getValueExpression(ctx, _type)); //right now this first line is commented out
((UIComponent) instance).setValueExpression(_name, _attr.getValueExpression(ctx, _type));
As far as I can tell, I haven't seen any repercussions to leaving both calls in place, but it feels like there should be a more elegant solution. I'll leave this open for discussion for a few days in case someone has another idea for a resolution before I check in the change.
In the meantime, I'll do some additional testing to make sure there aren't any side affects of making both calls.
Attachments
Issue Links
- duplicates
-
MYFACES-2677 Adapt CompositeComponentAttributesMapWrapper to changes from MYFACES-2633
-
- Closed
-
- relates to
-
MYFACES-2675 BeanValidation does not work with composite components
-
- Closed
-