[
http://jira.magnolia-cms.com/browse/MAGNOLIA-1455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20374#action_20374
]
gjoseph edited comment on MAGNOLIA-1455 at 1/14/09 9:27 PM:
-------------------------------------------------------------------
Started this locally, seems simple enough... except that the
ServletTemplateRenderer would be broken. Well -- it could always use the
WebContext and get the request/response from there, but it doesn't seem ideal.
What are the usecases for this renderer ? Delegating to a 3rd party framework ?
How does it work, how is Magnolia content passed around that ?
was (Author: gjoseph):
Started this locally, seems simple enough... except that the
ServletTemplateRenderer would be broken. Well -- it could always use the
WebContext and get the request/response from there, but it doesn't seem ideal.
What are the usecases for this renderer ? Delegating to a 3rd party framework ?
How does it work, how it Magnolia content passed around that ?
> Remove usage of HttpServletRequest and -Reponse in TemplateRenderer
> -------------------------------------------------------------------
>
> Key: MAGNOLIA-1455
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-1455
> Project: Magnolia
> Issue Type: New Feature
> Components: core, templating
> Reporter: Gregory Joseph
> Assignee: Philipp Bracher
> Fix For: 4.0
>
>
> This will allow getting rendered content remotely, for instance, and
> generally cleaner.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
