Following the growing adoptance of dynamic languages, frameworks and stacks we decided to make a as complete as possible integration of Grails and Magnolia. It turned out it was possible to make magnolia developement highly productive using it. It's now both open source and used in production. We will talk about why, how, benefits and do some live coding.
5. 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
7. WHY GROOVY
http://groovy.codehaus.org/
Tuesday, 4 September 12
8. WHY GRAILS
• Coding by convention
• Reloading built-in
• Based on Spring
• Full web stack
• Grails plugins
Tuesday, 4 September 12
9. MAGLEV GOALS
Integrate our favorite CMS
with our favorite web stack
Keep Grails intact
Keep Magnolia intact
Tuesday, 4 September 12
10. THE PROBLEM
Magnolia wants to control
the request lifecycle
Grails wants to control the
request lifecycle and building
and packaging
Tuesday, 4 September 12
11. 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
