[
https://issues.apache.org/jira/browse/TAP5-1312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Kirby updated TAP5-1312:
--------------------------------
Attachment: TAP-1312-diffs
Added code to RenderPhaseMethodWorker to cope with render methods taking
MarkupWriter2 as arguments instead of MarkupWriter.
No need for casting now - however the minimal cost of potentially coercing a
MarkupWriter to a MarkupWriter2 if required is incurred for each render method
invoked. There is probably a better way...
> Suggestion for a new DOM node that provides a callback at toMarkup time
> providing the PrintWriter
> -------------------------------------------------------------------------------------------------
>
> Key: TAP5-1312
> URL: https://issues.apache.org/jira/browse/TAP5-1312
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.2.2
> Reporter: Richard Kirby
> Attachments: TAP-1312-diffs, TAP-1312-diffs
>
>
> I would like a new org.apache.tapestry5.dom node that takes an interface
> which provides a callback method that is passed the PrintWriter being used
> when toMarkup is called.
> One usecase for this is where you want to insert a large chunk of raw text
> into a page that is coming from a streamable source (such as the output of a
> XSLT processor) and so is really not needed to be rendered into a String
> beforehand (which is what the MarkupWriter.writeRaw would require).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
