Components: introduce dependency injection (MAGNOLIA-2569)

[MAGNOLIA-3525] Support for using a custom TypeMapping in Content2Bean Created: 21/Jan/11  Updated: 09/Mar/12  Resolved: 09/Mar/12

Status: Closed
Project: Magnolia
Component/s: content2bean, core
Affects Version/s: None
Fix Version/s: 4.5

Type: Sub-task Priority: Neutral
Reporter: Magnolia International Assignee: Tobias Mattsson
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
is cloned by MAGNOLIA-4035 Revise content2bean Closed
dependency
depends upon MAGNOLIA-3517 Module descriptor additions Closed
relation
is related to MAGNOLIA-3599 IoC: pass the current component provi... Closed
is related to MAGNOLIA-2724 c2b: improve transformer discovery Closed
Template:
Date of First Response:

 Description   

While working on MAGNOLIA-2569, I had to change the Content2Bean interfaces, notably starting to pass the TypeMapping instance around.

There are probably better ways - since TypeMapping is some sort of global "cache", it shouldn't be necessary to pass it around. There was some (cyclic-) dependency issue, because Transformers needed an instance of TypeMapping.



 Comments   
Comment by Tobias Mattsson [ 18/Oct/11 ]

Moved to 4.5 since its in progress and will be released in 4.5

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