Adam,
thanks, indeed now I found the Tomhawk-777 jira. No way till they
fix it, my only chance to stay with Trinidad is to rewrite my dataTable
stuff through Trinidad-equivalent tr:table.
The dataTable is by far one of mostly used components, can I expect
equivalent functionalities in tr:table ? This is an overlapping area:
did anybody compare ?
Thanks -- Renzo
Adam Winer wrote:
If I remember correctly, this is a bug in dataScroller -
it assumes
behavior of CommandLinkRenderer that is not at all guaranteed,
in terms of encodeBegin()/encodeChildren()/encodeEnd() and where
all the content gets written.
-- Adam
On 12/21/06, Renzo Tomaselli <[EMAIL PROTECTED]> wrote:
Hi, I wonder if anybody succeeded in getting dataScroller working
under
Trinidad. Mine doesn't work anymore since I updated my web.xml to
Trinidad
stuff.
A dataScroller such as:
<t:dataScroller id="resultScroller" actionListener="#{
resultBean.paginator}" ....>
having a facet such as:
<f:facet name="next">
<h:panelGroup rendered="true">
<h:commandButton value="#{msg['result.scroller.next']}"
styleClass="nextPrevious" action=""/>
<t:graphicImage url=""
style="border: 1px""/>
</h:panelGroup>
</f:facet>
is rendered as:
<input id="_id50:result:_id409" name="_id50:result:_id409"
type="submit"
value="next"
class="nextPrevious">
<img src="" style="border: 1px">
<a id="_id50:result:resultScrollernext"
name="_id50:result:resultScrollernext"
class="OraLink" href=""></a>
the image element has no "onclick" attribute anymore, thus is not
active,
unlike the non-Trinidad version.
Furthermore, "next" button submits, but result is not as before (I'm
still
investigating about this).
Any idea ?
Thanks -- Renzo
|
