Nothing specific, but you might want to use a t:dataList instead of
dataTable if you're just looking for an iterator.

Also, take a look at this:

http://weblogs.java.net/blog/jhook/archive/2006/02/new_feature_for.html

I'm pretty sure Martin has this implement in Tomahawk as well,
although the name might be slightly different.  ExecuteOnCallback
might be the name in Tomahawk.

UIComponentPerspective.executeOn(javax.faces.context.FacesContext
context, ExecuteOnCallback callback)



On 1/21/07, Matt Tyson <[EMAIL PROTECTED]> wrote:

I've found a few posts in the ballpark of the issue I'm working on right now,
but no solutions.

I have a custom component inside a t:datatable.  I'm actually just using the
datatable to manage multiple instances of my custom component.

The custom component is a floatingPane (from dojo) that sends ajax data back
when it is moved, in order to preserve its location.

I find the component with findComponent using its ID (which is the datatable
id: id="floaterForm:paneTable:0:floatPane").

Its when I go to save the state that I find the problem.  There appears to
be only one floatingPane with a clientId of
floaterForm:paneTable:paneColumn:floatPane during the saveState method, and
the states of the multiple panes are confused with eachother.

Any ideas?

Thanks,

Matt
--
View this message in context: 
http://www.nabble.com/Datatable%2C-findComponent-and-saveState-tf3050405.html#a8479578
Sent from the MyFaces - Users mailing list archive at Nabble.com.


Reply via email to