Hansjörg Meuschel wrote:
oh ok... i don't know exactly all implementation details, however
what i know is that the t:datatable has some serious problems:
Example:
<h:form>
<t:datatable>
<t:column>
<h:inputText>
</ ...>
THIS WILL NOT WORK! (all input field get the same id)
<h:form>
<h:datatable>
<h:column>
<h:inputText>
</ ...>
THIS WILL WORK! (all input field get different ids)
This is the reason why the t:datatable can't be used with submittable
componenents! Or am I doing something very wrong here ??
[snip]
Note that there have been some problems reported recently regarding
tomahawk on sun's JSF RI implementation which *might* be related. I've
only tried this on the MyFaces JSF implementation.
[snip output showing h:dataTable generating unique ids, and t:dataTable
not doing so]
-> same client ids for each iteration are generated -> can't work!
I'm using JSF RI 1.1.01 / current myfaces version and it does not seem
that the panelgrid is the only component having this problem (09.01.2006
16:33: TabPane -> Form => Javascript-Error)
Do you have any ideas about that?
Ok, this *is* the same issue I referred to earlier. There is an
incompatibility between t:dataTable and the Sun reference
implementation's UIData class.
See:
https://issues.apache.org/jira/browse/MYFACES-1010
The current consensus seems to be that this is a problem with the Sun
RI. A workaround might be implemented in Tomahawk, but that's not going
to help you in the near future.
You could always move to using the MyFaces JSF implementation :-).
Otherwise it looks like you either need to use h:dataTable or create
your own version of t:dataTable containing one of the workarounds
described in the JIRA issue.
Note: I'm not sure if this is related to the original CollapsiblePanel
issue. Saurabh, are you using the Sun RI?
Regards,
Simon
