MAGNOLIA LEVITATING USING GRAILS Tuesday, 4 September 12
Oct 22, 2014
MAGNOLIA LEVITATING USING GRAILS
Tuesday, 4 September 12
Åke ArgéusKimmo Björnsson
WHO WE ARE?
15 years Java experience each
Contributed to Magnolia Blossom Spring integration
Tuesday, 4 September 12
Bonheur AB
100% MAGNOLIA
Tuesday, 4 September 12
Tuesday, 4 September 12
PREREQS
• From nothing to complete e-commerce system in 6 months
•Multiple teams
•Mixed content
• Easy to use and edit by editors
•Customizable and extendable, future-proof
•Utilize our existing Java experience
Tuesday, 4 September 12
+
CONCLUSION
Tuesday, 4 September 12
WHY GROOVY
http://groovy.codehaus.org/
Tuesday, 4 September 12
WHY GRAILS
•Coding by convention
•Reloading built-in
•Based on Spring
•Full web stack
•Grails plugins
Tuesday, 4 September 12
MAGLEV GOALS
Integrate our favorite CMS with our favorite web stack
Keep Grails intact
Keep Magnolia intact
Tuesday, 4 September 12
THE PROBLEM
Magnolia wants to control the request lifecycle
Grails wants to control the request lifecycle and building and packaging
Tuesday, 4 September 12
THE SOLUTION
Extends Grails with Magnolia (not the other way around)
Let Grails handle building and packaging
Hand over the request to Magnolia (entire filter-chain)
Extend Blossom to render templates and view with Grails
Modified UrlMapping to choose between Grails and Magnolia
Tuesday, 4 September 12
IN PRODUCTION
Tuesday, 4 September 12
WHEN IS IT USEFUL
Quick prototyping
Highly integrated apps
Database-backed content
Tuesday, 4 September 12
LIVE CODING
Tuesday, 4 September 12
Tuesday, 4 September 12