You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Henri Dupre (JIRA)" <ta...@jakarta.apache.org> on 2005/07/25 21:06:49 UTC
[jira] Created: (TAPESTRY-440) Public API for rendering pages inside a page/component
Public API for rendering pages inside a page/component
------------------------------------------------------
Key: TAPESTRY-440
URL: http://issues.apache.org/jira/browse/TAPESTRY-440
Project: Tapestry
Type: Improvement
Components: Framework
Versions: 4.0
Reporter: Henri Dupre
Priority: Minor
Many people seem to be using Tapestry to render emails inside the applications.
With tapestry 3.0, it was possible to store the get the value of the current form attribute, create a writer, render a page inside the current RequestCycle (for generating the email) and finally restore the form attribute.
With all the changes in Tapestry 4, this process is not straightforward to translate, and also I think this process should be hidden inside the framework.
Suggestion: add a method inside the IRequestCycle (or another Tapestry service) to render a page to a writer.
--
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
[jira] Resolved: (TAPESTRY-440) Public API for rendering pages
inside a page/component
Posted by "Jesse Kuhnert (JIRA)" <ta...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/TAPESTRY-440?page=all ]
Jesse Kuhnert resolved TAPESTRY-440.
------------------------------------
Fix Version/s: 4.1
Resolution: Fixed
The management of written content can now be controlled by providing your own implementation of the hivemind ResponseBuilder service configuration point. (to be documented soon)
> Public API for rendering pages inside a page/component
> ------------------------------------------------------
>
> Key: TAPESTRY-440
> URL: http://issues.apache.org/jira/browse/TAPESTRY-440
> Project: Tapestry
> Issue Type: Improvement
> Components: Framework
> Affects Versions: 4.0
> Reporter: Henri Dupre
> Priority: Minor
> Fix For: 4.1
>
>
> Many people seem to be using Tapestry to render emails inside the applications.
> With tapestry 3.0, it was possible to store the get the value of the current form attribute, create a writer, render a page inside the current RequestCycle (for generating the email) and finally restore the form attribute.
> With all the changes in Tapestry 4, this process is not straightforward to translate, and also I think this process should be hidden inside the framework.
> Suggestion: add a method inside the IRequestCycle (or another Tapestry service) to render a page to a writer.
--
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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org