tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Wyraz (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TAP5-1864) Block renderer helper / service
Date Mon, 11 Nov 2013 15:02:17 GMT

    [ https://issues.apache.org/jira/browse/TAP5-1864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13819011#comment-13819011
] 

Michael Wyraz commented on TAP5-1864:
-------------------------------------

[~uklance]  For doing such in a render phase there are better ways (namely intercepting "beforrender"/"afterrender"
and capture/remove the generated markup from the actual document).

> Block renderer helper / service
> -------------------------------
>
>                 Key: TAP5-1864
>                 URL: https://issues.apache.org/jira/browse/TAP5-1864
>             Project: Tapestry 5
>          Issue Type: New Feature
>          Components: tapestry-core
>    Affects Versions: 5.3.2
>            Reporter: Magnus Kvalheim
>         Attachments: RenderCommandToStringService.java, RenderCommandToStringServiceImpl.java
>
>
> I've seen several posts on the mailing lists asking for how to render blocks manually
in pages/components.
> Had a use case in this issue: https://issues.apache.org/jira/browse/TAP5-1863
> Basically I tried with:
> -------- 
> RenderCommand renderCommand = (RenderCommand)alertBlock; 
> MarkupWriter markupWriter = new MarkupWriterImpl(); 
> RenderQueueImpl renderQueue = new RenderQueueImpl(log); 
> renderQueue.push(renderCommand); 
> renderQueue.run(markupWriter); 
> alertManager.info(markupWriter.toString()); 
> -------- 
> Don't know if it's the 'correct' way of doing things so requesting a service or a helper
class available in core that does the job.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message