Details
-
Bug
-
Resolution: Won't Do
-
Neutral
-
None
-
4.4.3
-
None
Description
I'm involved in a project convinced to get Magnolia running in Grails.
We have an issue that Magnolia is not finding all resources it should when running in development mode. It is because it is a different classloader provided by Grails for the environment in that case.
ClasspathResourcesUtil.findResources does not find all resources it should with that particular classloader.
Grails wraps a URLClassLoader in an own 'ParentDelegatingClassLoader' which tricks Magnolia into that it isn't an URLClassLoader and it tries to find the resources in the wrong way.
Working on a patch for Magnolia to fix this.
Checklists
Acceptance criteria