[ http://issues.apache.org/jira/browse/TAPESTRY-545?page=all ]
Jesse Kuhnert closed TAPESTRY-545:
----------------------------------
Fix Version: unspecified
Resolution: Invalid
Assign To: Jesse Kuhnert
This is already handleable via the EnhancementWorker chain logic in hivemind. A
better solution should hopefully come out in the 4.1 release.
> 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
> Assignee: Jesse Kuhnert
> Priority: Minor
> Fix For: unspecified
>
> 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
