> Original reason for doing this is outlined here:
>
>
http://grails.1312388.n4.nabble.com/GORM-produces-errors-saying-I-have-duplicate-entries-on-some-hidden-API-code-td4632727.html>
> So... I started out by simply placing GrailsDomainBinder in src/java
> in the same package structure, assuming that the grails project itself
> is the first place the classloader would look for a class in it's
> first come first serve loading.
This is a minefield. In terms of 'run-app', you can use the script I
created here to look at the class loader ordering:
http://pastebin.com/vbEEJ402But remember that URLClassLoader is a _parent-first_ loader, i.e. it
asks the parent for a class before looking in its own search path.
This is probably why the grails-hibernate class is being used.
Another thing to bear in mind is that in WAR mode, there are probably
no guarantees of load order.
> So I unpacked grails-hibernate, changed the class, repacked, put back
> into my grails-2.1.0 folder.
> Inspecting the file in IDEA shows my changes all loaded (I have
> deleted the one in src/java), but when I run, the same error still
> happens, my changes do not take effect.
This is probably because the JAR is being taken from the Ivy cache,
not directly from $GRAILS_HOME. Try updating ~/.grails/ivy-cache/...
with your custom JAR.
In response to your earlier email, it looks like a good candidate for a JIRA.
Peter
--
Peter Ledbrook
Developer Advocate
VMware
t: @pledbrook
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
Locked
