[MAGNOLIA-3002] Swappable ClassUtil (ClassFactory) Created: 11/Jan/10  Updated: 23/Jan/13  Resolved: 02/Feb/10

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

Type: New Feature Priority: Major
Reporter: Magnolia International Assignee: Magnolia International
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
depends upon MAGNOLIA-3001 FactoryUtil/ClassUtil refactorings Closed
relation
is related to MAGNOLIA-3004 Content2bean should use ClassFactory ... Closed
Template:
Acceptance criteria:
Empty

 Description   

Modules need to be able to provide customized class loading mechanisms (Groovy integration for instance, but also modules that "fix" certain containers' class loading specifities, etc)

This is strongly linked to MAGNOLIA-3001, as it will provide some refactoring of the impacted classes (ClassUtil, ClasspathResourcesUtil, FactoryUtil, ...)



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

This is now feasible, following MAGNOLIA-3001. This is now named info.magnolia.objectfactory.ClassFactory.

Comment by Magnolia International [ 02/Feb/10 ]

ClassFactory can now be swapped at runtime; if the property info.magnolia.objectfactory.ClassFactory is set, it will be used.
The implementation hides some nasty details - such as the fact that when starting the system up, Classes/ClassFactory/Components/ComponentProvider is immediately being used, before we get a chance to register all properties (i.e before we can determine that we want to use a custom ClassFactory) - so it essentially checks for each call. See code/javadoc/comments for more details.

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