[
http://jira.magnolia-cms.com/browse/MGNLGROOVY-3?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25875#action_25875
]
Grégory Joseph commented on MGNLGROOVY-3:
-----------------------------------------
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.
> Provide a Groovy-aware ClassFactory implementation
> --------------------------------------------------
>
> Key: MGNLGROOVY-3
> URL: http://jira.magnolia-cms.com/browse/MGNLGROOVY-3
> Project: Magnolia Groovy Module
> Issue Type: New Feature
> Components: integration
> Reporter: Grégory Joseph
> Assignee: Grégory Joseph
> Fix For: 1.0
>
>
> Such that any class loaded by {{ClassFactory}} (formerly known as ClassUtil)
> could be a Groovy script/class.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
