Details
-
Improvement
-
Resolution: Fixed
-
Major
-
None
-
None
Description
The problematic point is that code which keeps a reference to an object will never see an reloaded changes. It would be more convenient and saver if the factory would return and cache a proxy instead.
Before this, code using such objects always had to get a fresh instance through the factory; once this is implemented, they can keep a reference (i.e get it in their constructor - potentially injected)
Checklists
Attachments
Issue Links
- is depended upon by
-
MAGNOLIA-2569 Components: introduce dependency injection
-
- Closed
-
-
MAGNOLIA-3080 Cleanup conundrum between FreemarkerHelper and FreemarkerConfig
-
- Closed
-
- is related to
-
MAGNOLIA-3001 FactoryUtil/ClassUtil refactorings
-
- Closed
-
-
MAGNOLIA-3059 Unable to replace implementation of the dynamically loaded class with its super class
-
- Closed
-
-
MAGNOLIA-2533 FactoryUtil$ObservedObjectFactory should gracefully handle components where a class is not specified
-
- Closed
-
-
MAGNOLIA-3011 ObservedComponentFactory.newInstance() should return a default implementation when the observed path doesn't exist yet
-
- Closed
-
-
MAGNOLIA-3079 ComponentProvider should lookup superclasses and interfaces of the required component
-
- Closed
-
-
MAGNOLIA-3086 Module instances could be proxies too
-
- Closed
-
-
MAGNOLIA-3444 Observed / proxied / c2b objects could improve their toString() behavior by showing their observed path
-
- Closed
-