>>>>> On Fri, 17 Feb 2012 13:32:54 -0800, Blake Sullivan <blake.sullivan_at_oracle.com> said:
B> I don't really agree. We have a usability problem, in that the current
B> behavior is unexpected. Even if the application developers do realize
B> they have problems, they run into:
B> a) The mismatch between what visitTree wants (clientIds) and what they
B> have (search expressions)
B> b) Reentrancy problems with visitTree and invokeOnComponent.
B> I believe that my suggested fix is the correct one, the issues are:
B> 1) It is hard
B> 2) This would almost certainly require yet another round of required
B> code changes for components that modify the EL Context, just like we did
B> when we introduced invokeOnComponent() and visitTree().
And 3) I don't feel the suggested fix has been articulated clearly
enough for the group or myself to understand and evaluate.
Can someone please step up and do that?
Ed
--
| edward.burns_at_oracle.com | office: +1 407 458 0017
| homepage: | http://ridingthecrest.com/