[
http://jira.magnolia-cms.com/browse/MAGNOLIA-2060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gregory Joseph closed MAGNOLIA-2060.
------------------------------------
Resolution: Won't Fix
Not the case anymore. We now have AbstractRenderer which takes care of setting
most of the context variables and so on. Further refactoring should further
improve the cases where custom renderers are needed for integration purposes,
but the JspTemplateRenderer can't be renamed to Default* now.
> Rename JspTemplateRenderer to DefaultTemplateRenderer
> -----------------------------------------------------
>
> Key: MAGNOLIA-2060
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2060
> Project: Magnolia
> Issue Type: Improvement
> Components: templating
> Affects Versions: 3.5.4
> Reporter: Jan Haderka
> Assignee: Philipp Bracher
> Priority: Minor
>
> It was shown in recent integration efforts that JspTemplateRenderer is robust
> and flexible enough to serve not only jsp based templates but also for
> example Spring Controller or Wicket based page templates. But it is confusing
> to for people to be told to use JspTemplateRenderer when what they want to
> render is not jsp at all.
--
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]>
----------------------------------------------------------------
