Hi Nourredine, well we gave up on jQuery's datatable and built our own searchable datatable solution. It's based on MongoDB, Tapestry's Grid, a GridDataSource similar to JpaGridDataSource and mongo-jackson-mapper[1]. It works fine in our backoffice but I think it doesn't scale well, if you plan to integrate it on a frequently used page (we're persisting a field in the session for convenience).
I'll check out Lance's approach, maybe I can use it to improve the code at Tapestry5-jQuery :-) Best, Christian [1] https://github.com/vznet/mongo-jackson-mapper Am 11.06.2012 um 10:09 schrieb Nourredine: > Hi Christian, > > I'm facing the exact same issue with the jquery datatable plugin. > > Just using a RenderCommand with the RenderQueue does not solve the issue > when blocks contain advanced components. > > So, I'm interested in your implementation which I will adapt to the Tapestry > 5.2 version > > Can you share the code you've developped to render a block using a > AjaxResponseRenderer or give me more details please ? > > Regards, > > Nourredine. > > -- > View this message in context: > http://tapestry.1045711.n5.nabble.com/Howto-render-a-block-and-put-it-into-a-JSON-reply-tp5486823p5713754.html > Sent from the Tapestry - User mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
