Can t:dataScroller's for-attribute reference UIData object in another form?

[Rønnevik, Eivind <ei...@kadme.com>]

Hi! 
 
My question is this:
 
I have a dataScroller, and want to specify the for-reference to a dataTable, only thing is that I see the need of having the two objects (scroller and table) in two different forms (layout issues). 
 
I've tried something like this, with no success:
 
<t:dataScroller id="dataScroller1" for="main:dataTable">
 
Then of course I have an <h:form> with id ="main", and in this form I have the dataTable with id="dataTable".
 
But I still get this "IllegalArgumentException: could not find UIData referenced by attribute dataScroller@for = 'main:dataTable'  
 
Ideas anyone? Is this possible at all?
 
Regards,
 
Eivind

Re: Can t:dataScroller's for-attribute reference UIData object in another form?

[Mike Kienenberger <mk...@gmail.com>]

On 8/23/06, Rønnevik, Eivind <ei...@kadme.com> wrote:
> I have a dataScroller, and want to specify the for-reference to a dataTable,
> only thing is that I see the need of having the two objects (scroller and
> table) in two different forms (layout issues).
>
> I've tried something like this, with no success:
>
> <t:dataScroller id="dataScroller1" for="main:dataTable">
>
> Then of course I have an <h:form> with id ="main", and in this form I have
> the dataTable with id="dataTable".
>
> But I still get this "IllegalArgumentException: could not find UIData
> referenced by attribute dataScroller@for = 'main:dataTable'
>
> Ideas anyone? Is this possible at all?

You'll probably need to submit a patch to be able to support this.   I
suspect it uses a relative "id" rather than the clientId.   A patch
could try to find the dataTable using the client id if the relative id
search fails.

Of course, it's considered best practice to use only one form per page :-)