unlock enterprise databases to create new online services with magnolia and grails

WebCastPeter Wayner

Magnolia + Grails = Maglev

Version 1.1 Magnolia is a registered trademark owned by Magnolia International Ltd.

WebCastPeter Wayner

MaglevTable-driven data with GrailsTemplate-driven pages with Magnolia

Is it possible to mix the ease of Grails with the

Magnolia?

Yes! With Maglev, a plugin

Grails is a Java-based Web App FrameworkGrails is open sourceGrails is template-driven (GSP and JSP)Grails is extendable with plugins.

Magnolia is a Java-based Content Management SystemMagnolia is open sourceMagnolia is template-driven (Freemarker and JSP)Magnolia is extendable with plugins.

Magnolia is Similar

Developed by Kimmo Björnsson and Åke Argéus, Lead Developers, Bonheur ABThey saw that the two tools that complemented each other well.They turned Magnolia into a plugin that lives in Grails.

Invention

Maglev bundles together all of Magnolia into a Grails plugin.It’s plugged into Grails, but Magnolia ends up driving the front.Grails handles the table-driven objects.Magnolia handles the templates

Let’s mix them together

Rapid prototyping. Grails builds databases quickly.Data/Content integration. Magnolia knits together content well.Separation of code from presentation. (Grails handles backend, Magnolia the front.)

Benefits

Affiliate marketing for a web site needs a table of URLs. If someone clicks on the URL, the web site gets some revenue.Lets store them in a table.Display them in a Magnolia template.

Example

class AffiliateItem {

String name // The item being advertised.

Date dateCreated // When started.

String url // Where the item can be purchased.

String shortDescription // A short description.

String longDescription // A long description.

Date startDate // When available.

Date stopDate // The last day it is available.

Grails just needs an object definition

class AffiliateItem {

static constraints = {

name blank:false, unique:true

url url:true,blank:false, unique:true

shortDescription maxSize:26

longDescription widget:textarea

/// ….

Grails lets you add constraints

class AffiliateItemController{

static scaffold = true

Just add a controller

Grails builds CRUD (create, update, delete) routines for object tables. You start up Grails and it analyzes your object definition.Then it creates all of the code necessary to let you build up tables filled with the objects.

One button and Grails Finishes

package testgrails1

import org.springframework.dao.DataIntegrityViolationException

class AffiliateItemController {

static allowedMethods = [save: "POST", update: "POST", delete: "POST"]

def index() {

redirect(action: "list", params: params)

def list() {

params.max = Math.min(params.max ? params.int('max') : 10, 100)

[affiliateItemInstanceList: AffiliateItem.list(params), affiliateItemInstanceTotal: AffiliateItem.count()]

def create() {

[affiliateItemInstance: new AffiliateItem(params)]

def save() {

def affiliateItemInstance = new AffiliateItem(params)

if (!affiliateItemInstance.save(flush: true)) {

render(view: "create", model: [affiliateItemInstance: affiliateItemInstance])

return

flash.message = message(code: 'default.created.message', args: [message(code: 'affiliateItem.label', default: 'AffiliateItem'), affiliateItemInstance.id])

redirect(action: "show", id: affiliateItemInstance.id)

def show() {

def affiliateItemInstance = AffiliateItem.get(params.id)

if (!affiliateItemInstance) {

flash.message = message(code: 'default.not.found.message', args: [message(code: 'affiliateItem.label', default: 'AffiliateItem'), params.id])

redirect(action: "list")

return

[affiliateItemInstance: affiliateItemInstance]

def edit() {

return

[affiliateItemInstance: affiliateItemInstance]

def update() {

return

if (params.version) {

def version = params.version.toLong()

if (affiliateItemInstance.version > version) {

affiliateItemInstance.errors.rejectValue("version", "default.optimistic.locking.failure",

[message(code: 'affiliateItem.label', default: 'AffiliateItem')] as Object[],

"Another user has updated this AffiliateItem while you were editing")

render(view: "edit", model: [affiliateItemInstance: affiliateItemInstance])

return

affiliateItemInstance.properties = params

if (!affiliateItemInstance.save(flush: true)) {

render(view: "edit", model: [affiliateItemInstance: affiliateItemInstance])

return

flash.message = message(code: 'default.updated.message', args: [message(code: 'affiliateItem.label', default: 'AffiliateItem'), affiliateItemInstance.id])

redirect(action: "show", id: affiliateItemInstance.id)

def delete() {

return

affiliateItemInstance.delete(flush: true)

flash.message = message(code: 'default.deleted.message', args: [message(code: 'affiliateItem.label', default: 'AffiliateItem'), params.id])

catch (DataIntegrityViolationException e) {

flash.message = message(code: 'default.not.deleted.message', args: [message(code: 'affiliateItem.label', default: 'AffiliateItem'), params.id])

redirect(action: "show", id: params.id)

Just some of the code built by Grails for free

What the user sees

Magnolia just needs a controller that can search the tables for what it wants.A template can format what is found.

What Magnolia Does

import info.magnolia.module.blossom.annotation.Template

@Template(id = "grailsModule:pages/demoTemplate", title = "Demo

template")

class MainTemplateController {

def index() {

[count:AffiliateItem.count(), items:AffiliateItem.list()]

MainTemplateController

There are some static methods for looking through the tables of AffiliateItems.

template")

def index() {

The index method calls the static search methods and bundles the results into a data structure for the template. You can add extra search logic and filtering here.

template")

def index() {

The Template annotation connects the controller with the templates.

template")

def index() {

There are <i> <%= count %></i> AffiliateItems

<g:each in="${items}" var="x">

<li><a href=”${x.url}”>${x.name}</a> --

<i>${x.longDescription}</i></li> </g:each>

</div>

Index.gsp

The count is just a number collected from the AffiliateItem.count() static routine in the Controller.

</div>

Index.gsp

Grails loops through the list of objects created by the AffiliateItem.list() method in the Controller.

</div>

Index.gsp

Index.gsp becomes a template for MagnoliaMagnolia glues it together into the web site like all of the other templates and blocksThe Grails blocks sit next to the others.

Magnolia Takes Over

More complicated templates.More logic in the Controllers.Magnolia glues them all together in a nice layout.

What Next?

Introduction http://wiki.magnolia-cms.com/display/TALKOOT/Creating+Database-driven+Web+Applications+with+Magnolia+CMS,+Groovy+and+Maglev

Maglev quickstart

https://github.com/Bonheur/maglev/wiki/Quick-

Maglev downloads

https://github.com/Bonheur/maglev/downloads

Maglev JIRA site. http://

jira.magnolia-cms.com/browse/MAGLEV

http://www.magnolia-cms.com/community/magnolia-

conference/program/presentation-day/

presentations/bonheur-ab.html

Resources

28 Version 1.1 Magnolia is a registered trademark owned by Magnolia International Ltd.

Section title with abstract

Section titlewith image

Lay the foundation for future successImprove usabilitySimplify customizationLower the entry barrierDon’t change what worksProvide a migration path

List of points without subtopics

Editor

• Exposed by View (HasEditors)

• Populate View with data

• Retrieve values entered by user

Driver

• Injects values into editors

• Updates underlying model (node, bean)

• Validates data

Used in various editable views

• DialogView, TreeView, ParagraphEditView…

Title and bullets

Enterprise Edition

• Best choice for mission critical websites

• Supported by the vendor

• Advanced enterprise features

• Visible source via Magnolia Network Agreement

• Cost effective

• Double the Speed

Community Edition

• Basic content management functionality

• Supported by the community

• Free for unlimited use

• Open source

• Cost effective

• Double the Speed

Title and bullets – 2 columns

POJOs (Definitions)

• Dialogs, trees, actions

• Vaadin independentContributed in various ways

• Configuration

• Annotations

• ProgrammaticallyUI Builder builds the Vaadin components

Title, bullets & picture

Title and picture horizontal

Series 1, 2, 3, 4Each step one slide

1 2 3 4

Where does great content come from?

It takes about ten seconds to explain how to create

content!

Clouds

DevelopmentAuthoring

Accessibility

Configuration UIWizards

Developer mode

AdminCentralPage editing

ClipboardSaved lists

Search

KeyboardLTR/RTL

MobileTouch

DD.MM.YYYY at Venue/Customerfirst.last@magnolia-cms.com

First Last, RoleMagnolia International Ltd.

www.magnolia-cms.com

Final slide

unlock enterprise databases to create new online services with magnolia and grails

Technology

groovy & grails

curso grails

grails services

why grails

tomas grails

grails 101

grails lucenecacherdfperformance

neo4 + grails

charla grails

grails latinoware

practical grails

grails queries

grails acl

grails - crud

jeter - magnolia, texas · magnolia high school magnolia...

grails transactions

framework grails...framework grails ...

new varieties of magnolia biondii and magnolia cylindrica...

grails portal

grails workshops