Details
-
New Feature
-
Resolution: Fixed
-
Major
-
None
-
None
-
-
Empty show more show less
Description
After using content2bean in some places the idea of using it as a general mechanism came up. Instead of introducing spring to wire up the objects we could do the following:
Main idea:
- in addition of defining the implementation class as a property (as we do today) we allow defining a path to the configuration in the config repository
- The FacotryUtil uses content2bean to create the objects
- FactoryUtil starts an observation for the singletons (no extra-coding for reloading, synchronization properly handled, ...)
Add ons:
- To allow complex transformations a class/type based transformer registration is supported
- For objects which are created before the repository is present (module regisration, content repository, ...) we could use the same mechanism by using a properties file based (mock) hierarchy manager.
This would make the system highly flexible without changing much. ALL static methods except those to get the instances will be deprecated.
Checklists
Acceptance criteria