Hi Sylivain,
On 6/20/05, Sylvain Vieujot <[EMAIL PROTECTED]> wrote:
> I just find maybe a more elegant way to solve this.
> It still involves using dynamically setting the clientId, but instead of
> adding a new attribute to the components, we could add a new rowId attribute
> to the x:dataTable :
> <x:dataTable var="email" rowId="#{email.unid}" ...>
The problem with this approach is that it changes the interpretation
of the scope in which the "email" variable will be evaluated.
Variables exposed by components should only have scope inside the
component, not at the component itself.
For example, the variable "email" may already non-null on the request scope.
Kind Regards,
John Fallows.
