You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Jesse Kuhnert (JIRA)" <ta...@jakarta.apache.org> on 2005/08/16 16:43:54 UTC
[jira] Commented: (TAPESTRY-545) Hook into the rendering process for AJAX improvement
[ http://issues.apache.org/jira/browse/TAPESTRY-545?page=comments#action_12318898 ]
Jesse Kuhnert commented on TAPESTRY-545:
----------------------------------------
This is being worked on in a related project, tacos.sourceforge.net. Reference implementation will be available soon.
> Hook into the rendering process for AJAX improvement
> ----------------------------------------------------
>
> Key: TAPESTRY-545
> URL: http://issues.apache.org/jira/browse/TAPESTRY-545
> Project: Tapestry
> Type: Improvement
> Components: Framework
> Versions: 4.0
> Reporter: Markus Joschko
> Priority: Minor
>
> I added this feature request in the hope, that we might find a solution on how to simplify the AJAX support in tapestry.
> It currently requires a special "Part" component which exchanges its markupwriter during rendering. As all components not contained in such a "Part" use a Nullwriter, this approach allows to only render specified components.
> The disadvantage with this is, that the part component is absolutely required. It would be much nicer if all components could be marked as "to be rendered".
> For a discussion which approaches are possible see http://thread.gmane.org/gmane.comp.jakarta.tapestry.devel/6734
> At the end I can only see one possibility (or maybe two, but the second one is dirty):
> -add a wrapMethodImplementation(Class,MethodSignature,String,String) method to the EnhancementOperation interface which allows to do kind of AOP magic to the renderComponent method of each component. This would allow to switch the markupwriter in all renderComponent methods of all components.
> the disadvantage: the enhancementworker who does this must come very late in the chain. Otherwise other enhancementworkers could add code before or after the wrapped code.
> -the dirty one: using a little enhancement for the prepareforRender method in combination with threadlocals, the partialservice and a special markupwriter could achieve the same. But this would require to make the markupwriter more clever than it should be. not nice.
> As already mentioned in the e-mail discussion: I can't see any other possibilities. But maybe someone else?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org