Hi all -

The 4.1 version seems very exciting: the @EventListener annotation is really cool and easy to use.

Currently I am working on a Project with a very extensive use of XHR using Dojo and currently Tapestry 4.0

In evaluating 4.1 it seems to me, a great work has been done to enable render and process XHRs - it seems to me however that some *abstraction* and *extensibility* is missing.

Talking concrete:

The ResponseBuilder (Dojo, Default, JSON) are built around an Interface that enables these three.

The Tapestry Javascript Response renderer (tapestry.load) handles a few actions : JavaScript processing and "replace by id".

I would suggest making both response builder implementations and tapestry.load more extendable, adding pluggable actions to both.

Cheers,
Ron



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to