I would argue that component event requests is where Tapestry
meets action-based frameworks.
If we forget that fact that those event urls expose a bit of the internal
structure of the application and over time may change, then you really
get to an action-based workflow.

On Tue, Nov 23, 2010 at 20:25, Michael Gentry <mgen...@masslight.net> wrote:
> I recently integrated the JQuery-based DataTables[1] library into one
> of my Tapestry applications.  I had previously used the HTML approach
> (rendering all of the HTML for the table via the TML and then let the
> DataTable augment the HTML table), but went with the AJAX option to
> handle large result sets.  I was unsure how to handle the AJAX calls
> with Tapestry, but after a little digging I figured it out and it was
> much simpler than I feared.  I created an event/handler in my
> component that processed the AJAX request and returned JSON to the
> DataTable.  It ended up being a component with ~100 lines of code.  I
> was pretty happy with the flexibility of both Tapestry and the
> DataTable.  I'm not convinced an action-based framework is any easier.
>
> mrg
>
> [1] http://www.datatables.net/
>
>
> On Tue, Nov 23, 2010 at 12:06 PM, Piero Sartini <li...@pierosartini.de> wrote:
>> Yeah - you could do this, but a lot of problems will arise. You don't
>> want to do this, I've tried it.
>> In the end you give up the advantages of components and gain nothing.
>> And its still more complex to use than in an action based framework,
>> especially if it comes to AJAX.
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
>



-- 
Andreas Andreou - andy...@apache.org - http://blog.andyhot.gr
Tapestry PMC / Tacos developer
Open Source / JEE Consulting

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org

Reply via email to