Thanks to both of you. Josh, adding the JSON result processor to the traditional requests I suppose it is harmless. But, the result processor for the blocks I think it is the RenderCommandComponentEventResultProcessor, and it does many things with Partial Markup Renders/Filters, etc, and it even uses an AjaxFormUpdateController service, so I do not know if I it is safe to use this for traditional requests...
I know it is not "normal" the need to render partials in traditional requests, but I think for integration with libraries or other software, it can be very useful… not directly the HTML, but, as Tapestry does for Ajax requests, a JSON object with an HTML partial. Regards, Raul. -- View this message in context: http://tapestry-users.832.n2.nabble.com/plupload-with-Tapestry-tp5862187p5864972.html Sent from the Tapestry Users 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
