use another classloader to load user's jars and classes

Details

Type: Improvement
Status: Open
Priority: Critical
Resolution: Unresolved
Affects Version/s: 1.0.3
Fix Version/s: 3.0
Component/s: None
Labels:
None

Description

It seems that Grails load all jars and classes with the same classloader.

As we all know, Grails is developed based on a lot of third part jar files, such as spring.jar

When we want to use other version of jar files which are placed in the PROJECT_HOME/lib directory, we will encounter some conflicts between different versions of classes with same qualifiable class name.

I have a crazy idea, why not treat the app created by developers as a special plugin of Grails?

If GRAILS-2221 is resolved, we can solve the conflict problems easily.

Thanks,
Daniel.Sun

Activity

Ascending order - Click to sort in descending order

Hide

Permalink

David Mabe added a comment - 29/Jul/08 10:13 AM

I believe this issue is why jar files from ancillary projects of mine that use groovy classes do not work.

Is there a more elegant workaround than copying the source files into my grails project source tree?

I could try building a war file and using Tomcat instead of Jetty but I'd lose my ability to run the grails console to script against gorm domain classes and I'm not 100% certain that would work unless I deployed my 3rd party jars and groovy all jar to <catalina_home>/common/lib

Show

David Mabe added a comment - 29/Jul/08 10:13 AM I believe this issue is why jar files from ancillary projects of mine that use groovy classes do not work. Is there a more elegant workaround than copying the source files into my grails project source tree? I could try building a war file and using Tomcat instead of Jetty but I'd lose my ability to run the grails console to script against gorm domain classes and I'm not 100% certain that would work unless I deployed my 3rd party jars and groovy all jar to <catalina_home>/common/lib

Graeme Rocher made changes - 18/Sep/08 9:11 AM