Grails is an agile and productive web development stack based on Groovy, Spring, Hibernate and other best-of-breed OSS components and AJAX toolkits.
| Title | JCR plugin for Grails |
| Keywords | Grails, Groovy, JCR, plugin |
| Description | Provide ORM like behaviour for domain classes onto a JCR repository as well as other JCR integration points. |
| Deliverables | A grails plugin for abstract the usage of JCR specification and facilitate to create content oriented web applications. Battery of unity-test and functionality test of code. |
| Mentor(s) | Graeme Rocher, Grails project lead |
| Title | Include plugin for Grails |
| Keywords | Grails, Groovy, JCR, plugin |
| Description | Using g:render tag tou should pass model/collection/bean to a template. I can see some problems with render behaviour, for example in a home page: The HomeController shouldn't worry to use gorm/services calls, this should be responsibility to controllers from each logic entity. A home page with news, events, forum, tags, last users... force HomeController to call News.find, Events.find, Forum.find, Tags.find, User.find... breaking DRY principle.
This plugin provides better DRY for complex web pages, the plugin usage maybe <g:include controller="controllerName" action="actionName"/> The called controllers wouldn't change any line of code, the changes should be at views and templates only. |
| Deliverables | A grails plugin with tags. |
| Mentor(s) | Graeme Rocher, Grails project lead |
Labels
(None)