[MAGNOLIA-2383] TemplateRenderer should be instantiated using content2bean Created: 18/Sep/08  Updated: 02/Dec/13  Resolved: 02/Dec/13

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: 3.6.1
Fix Version/s: None

Type: Improvement Priority: Major
Reporter: Fabrizio Giustina Assignee: Philipp Bärfuss
Resolution: Duplicate Votes: 0
Labels: content2bean, ioc
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
is depended upon by MAGNOLIA-2384 display pages only with defined exten... Closed
relation
is related to MAGNOLIA-2369 Templates should be instanciated with... Closed
is related to MAGNOLIA-2569 Components: introduce dependency inje... Closed
is related to MGNLSTK-577 Make it configurable what classes are... Closed
is related to MAGNOLIA-1564 Accessing a page without proper exten... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:

 Description   

TemplateRendererManager should use content2bean, this will make template renderer more easily configurable



 Comments   
Comment by Magnolia International [ 19/Jan/10 ]

for the record - this should be fairly straightforward for ParagraphRenderers (via PRManager). For TemplateRenderers (TRManager), we'd need either a custom c2b transformer or update tasks, since template renderers are currently configured with type and renderer properties (which "should be" name and class if we want straighforward c2b conversion)

Comment by Tobias Mattsson [ 02/Dec/13 ]

This is the case since 4.5.

Generated at Mon Feb 12 03:36:11 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.