[MGNLGROOVY-3] Provide a Groovy-aware ClassFactory implementation Created: 13/Jan/10  Updated: 25/Nov/13  Resolved: 10/Feb/10

Status: Closed
Project: Magnolia Groovy Module
Component/s: integration
Affects Version/s: None
Fix Version/s: 1.0

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
is depended upon by MGNLGROOVY-6 Ability to load groovy classes off th... Closed
duplicate
duplicates MAGNOLIA-635 Using rhino (javascript) for configur... Closed
Template:
Acceptance criteria:
Empty

 Description   

Such that any class loaded by ClassFactory (formerly known as ClassUtil) could be a Groovy script/class.



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

Just realized I probably made the wrong decision: in the original patches, we were first loading from the regular ClassLoader, THEN from Groovy. I did the opposite so that you could override ANY class loaded through ClassFactory even without configuring anything. It probably does not have much of an impact, but still some. I guess for things like Models, it might be interesting to bypass the regular CL, but for most of the system, going first to the regular CL is probably the best. There might be an even better approach, by dissecting the GroovyCL, and just poke the resource loader to see if such a script exists, before attempting any class loading.

Generated at Mon Feb 12 05:54:37 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.