grails-3.1

I'm trying to map existing tables in a GORM/Grails app. Most of the tables have composite primary keys (not my choice). I'm finding that when I map an association to a class (parent of a child) where the composite key of the parent class contains an association to a class with a composite key also (grandparent), GORM doesn't bother to check the mapping of the grandparent class and subs in a non-composite key. Child class Child implements Serializable { Parent parent String name belongsTo= [parent: Parent] static mapping= { id(composite: ['parent', 'name']) } } Parent class Parent implements

In Grails 2.x, to allow following symbolic links, we can add following in the scripts/_Events.groovy : eventConfigureTomcat = { tomcat -> def ctx = tomcat.host.findChild("") ctx.allowLinking = true // Follow soft links } How can we achieve the same in Grails 3? I've tried creating the same script file in src/main/scripts directory in Grails 3 but didn't help. Edit: I also tried adding following line in Bootstrap.groovy : Holders.getServletContext().allowLinking = true GitHub issue #10045 Finally, I've figured out the solution for following symbolic link in Grails 3 with the help of examples

We would like to use Log4j2 as the log binding with grails 3. From what I can figure out so far. We have many subordinate dependencies that use a variety of loggers, so we need to use the SLF4J API. Then, instead of letting grails / groovy / spring re-direct the SLF4J API to the Logback binding, we need to re-direct each to the Log4j2 binding. Since grails 3 uses the Logback binding, I am planning to go through each dependency in the build.gradle, exclude the Logback binding, and include the Log4j2 binding. Will this work? Update: Yes Do we also need to bridge the Log4j2 API to the SLF4j API?

In grails 2.x, we were allowed to add an in place plugin by adding following in BuildConfig.groovy grails.plugin.location."my-plugin" = "../my-plugin" My question is, can we add our local plugins similarly in-place in grails3.0 as well or there is some other way to do this in grails. Actual purpose is to test the plugin whether it's working properly or not before pushing it to bintray. Yes, there is. Grails 3 is based on Gradle so multi-project gradle builds solve your issue. Basically you add dependency as: compile project(':../my-custom-plugin') and has to modify settings.gradle to include

I'm trying to disable automatic reload/recompiling in Grails 3.1 as I would like to use JRebel instead. I find springloaded rather limited, but more importantly is constantly fails with File /Users/engrun/Development/projects/grailsPoc/grails-app/controllers/grailsPoc/HelloController.groovy changed, recompiling... java.lang.IllegalAccessException: Class org.springsource.loaded.ReloadableType can not access a member of class org.springframework.aop.framework.CglibAopProxy$ClassLoaderAwareUndeclaredThrowableStrategy with modifiers "public" I have tried all kinds of settings that I have found