grails 3 inside and out

Unless otherwise indicated, these sl ides are © 2013-2015 Pivotal Software, Inc. and l icensed under a Creat ive Commons Attr ibut ion-NonCommercial l icense: ht tp: / /creat ivecommons.org/ l icenses/by-nc/3.0/

SPRINGONE2GXWASHINGTON, DC

Grails 3 Inside & OutBy Graeme Rocher

@graemerocher


Who we are?

Jeff Scott Brown Object Computing Inc. @jeffscottbrown [email protected]

2

Graeme Rocher Object Computing Inc. @graemerocher [email protected]

mailto:[email protected]

mailto:[email protected]


Grails + OCI• OCI focused on Grails• Full service support

– Consulting– Training– Support

• Commitment to engineering • Grails team at OCI growing

– Come speak to us!

3

Unless otherwise indicated, these sl ides are © 2013-2015 Pivotal Software, Inc. and l icensed under a Creat ive Commons Attr ibut ion-NonCommercial l icense: ht tp: / /creat ivecommons.org/ l icenses/by-nc/3.0/ 4

More at ociweb.com/grails

Visit the OCI’s Table #2 to meet our Grails Team!

Graeme Rocher Jeff Brown

Dave Klein Colin Harrington


Agenda• Plugins & Traits• Plugins & Events• Configuration API• Code Generation API• Gradle & The Shell

5


The Example• Build a Mail Sender Plugin

• Trait• Events• Configuration• Code Generation

6



Plugins & Traits


Adding Behaviour with Traits• Use Enhances to add behaviour

8

importgrails.artefact.*

@Enhances('Controller')traitMyTrait{voidmyNewMethod(){…}}


Core Grails Traits• Controller - implemented by all controllers• DomainClass - implemented by all domain classes

• GormEntity - implemented by all GORM entities• Service - implemented by all services• TagLibrary - implemented by all tag libraries• Interceptor - all Grails interceptors• Events - Any object that wants to send events

9



Events


Events• Any class that implements the Events trait can send and receive events• Controllers and services implement the trait by default• You can effectively decouple systems using an event driven approach• Fits nicely with reactive programming• Events are built on the Reactor framework

• http://projectreactor.io

11

http://projectreactor.io


Events• Use on to listen and notify to send or combine with sendAndReceive

12

notify('mail:sent',eventFor(message))

on('mail:sent'){Event<TYPE>event->//dostuff}


Events• The Consumer and Selector annotations from Spring Reactor work too!

13

@ConsumerclassMyService{

@Selector('mail:sent')voidmailEventListener(MailMessagemsg){//dostuff}}



Configuration API


Configuration API

15

booleanisFooEnabled=config.getProperty('foo.bar',Boolean,true)

//or

@Value('foo.bar')booleanisFooEnabled


Plugins & Configuration• Applications inherit plugin configuration• You should keep your plugin configuration minimal• Plugin configuration defines the default values• Applications can override any plugin provided value

16



Code Generation & Grails


Code Generation Scripts• Go in src/main/scripts in plugins or applications• All scripts subclass the GroovyScriptCommand class• Some handy properties

• gradle - for invoking Gradle• ant - for invoking Ant• methodMissing - for invoking other code gen commands

• Useful traits• TemplateRenderer - for rendering templates• FileSystemInteraction - for interacting with the file system

18


Code Generation Scripts• The model method exposes a Model interface for introspecting conventions

19

interfaceModel{StringgetClassName()StringgetFullName()StringgetPackageName()…StringgetLowerCaseName()Stringconvention(StringconventionName)Map<String,Object>asMap()}


DSL for Code Generation Scripts

20

description("Createsaservicethatsendsamail"){usage"Thisdoescoolsstuff"}

defmodel=model(args[0])

rendertemplate:template('MailService.groovy'),destination:file("grails-app/services/${model.packagePath}/${model.convention('Service')}.groovy"),model:model



Gradle & The Shell


Gradle & The Shell• Create Gradle tasks that invoke your app

• Without knowing any Gradle! ;-)

22

classMailBatcherCommandimplementsApplicationCommand{booleanhandle(ExecutionContextcontext){//DOSTUFFreturntrue}}


Gradle & The Shell• Just add to build.gradle build class path and run the command

23

classpath'org.grails.plugins:mailSender:0.1-SNAPSHOT'

gradlebatchSendMailgrailsbatch-send-mail


Summary• Grails 3 provides powerful techniques to build plugins that empower your

application• The core philosophy of plugins and modular applications continues• Through traits and events Grails 3 is more powerful that ever before!• Grails’ internals are all based on the described techniques

24


Q & A

25

Unless otherwise indicated, these sl ides are © 2013-2015 Pivotal Software, Inc. and l icensed under a Creat ive Commons Attr ibut ion-NonCommercial l icense: ht tp: / /creat ivecommons.org/ l icenses/by-nc/3.0/ 26


The OCI Grails Team is growing — will You join us?


Stay Connected.

Web: grails.orgStackOverflow: http://stackoverflow.com/tags/grails Slack: http://slack-signup.grails.org Twitter: twitter.com/grailsframeworkLinkedIn: http://linkedin.com/groups/Grails-User-Group-39757

27


http://grails.org

http://stackoverflow.com/tags/grails

http://slack-signup.grails.org

http://inkedin.com/groups/Grails-User-Group-39757

grails 3 inside and out

Technology