Hello Roger
Ok, that's what I wanted to know. I thought that this issue is a spec doc
change in UIData, but it also involves implement
UIData.getContainerClientId, and make other doc changes on UIData.visitTree
and UIData.invokeOnComponent. I'll revert those changes on myfaces core
2.0.x, but include them on tomahawk for jsf 2.0.
Yes, it could be good if this issue is considered for jsf 2.1
Thanks for the information.
regards,
Leonardo Uribe
2010/7/13 Roger Kitain <roger.kitain(a)oracle.com>
Hello Leonardo,
We cannot make this kind of change for Rev A. Only supposed to be spec doc
changes.
But I see this issue is currently unscheduled - I'll see if we can schedule
it in for one of our 2.1 milestones.
I'm going to be revisiting a bunch of those issues to prioritize
accordingly.
Thanks, Roger.
On 7/13/10 3:11 PM, Leonardo Uribe wrote:
> It was told it is better to change the behavior of UIData.getClientId, to
> it does not include the id and instead set this behavior on
> UIData.getContainerClientId. This requires some small changes on
> UIData.invokeOnComponent (call UIData.getContainerClientId instead
> UIData.getClientId) and other methods, but it seems the way to go. Could you
> please consider this change to be included in Rev A?
>
--
roger.kitain(a)oracle.com
https://twitter.com/rogerk09
http://www.java.net/blogs/rogerk