|
Sponsored Links
Resources
Enterprise Java
Research Library
Get Java white papers, product information, case studies and webcasts
|
News
News
News
|
Messages: 8
Messages: 8
Messages: 8
Printer friendly
Printer friendly
Printer friendly
Post reply
Post reply
Post reply
XML
XML
XML
|
 |
Graeme Rocher on the Grails Plugin Architecture
Grails is an MVC action-based web framework inspired by the principle of "convention over configuration." It leverages many of the features of Groovy, Spring MVC and Hibernate. A wide range of plugins are available for rich client/Ajax development, Web services and performance management.
In this presentation, recorded at the recent Grails Exchange event in London (organized by Skills Matter), Grails co-founder Graeme Rocher explains how to go about getting the best out of the Grails plug-in architecture by demonstrating how to create re-usable plugins that can be distributed, installed and managed.
Dowload the slides for this presentation here.
Watch other Tech Briefs
|
|
|
Message #243016
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Re: Graeme Rocher on the Grails Plugin Architecture
i'm amazed that this hasn't been done before. i use grails quite a lot and plugins work really well, but there are times that i wish i could bundle non-grails plugins without having to set them up as grails plugin projects first.
there are so many candidates for plugins in most projects, like login/logout screens, forgotten passward etc., it would be great to see this idea fleshed out a little more with the grails dependency.
|
|
|
Message #243020
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
grails
Due all respect, i hear crickets when subject is Grails in TheServerSide. Grails may be a decent project, but to me that project is losing big time because it includes the word "rails" word in it. it sounds like a cheap wanna be. And i still do not have interest in neither.
|
|
|
Message #243021
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
A Grails Convert ...
I was a Grails Skeptic like you , seeing it as a poor Man's version of Ruby on Rails (and so preferring to spend my time on JRuby).
However, after seeing some of Groovy / Grails presentations at the IJTC I've changed my mind, or at least been persuaded to give it a 2nd look.
The main reason for my change of mind is the syntax. Groovy / Grails syntax is a lot more 'natural' for Java programmers. Now I know Ruby syntax is easy to pick up, but Groovy is even easier (and sometimes there are good reasons to be lazy!)
|
|
|
Message #243024
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Re: A Grails Convert ...
Grails looks interesting. I spent a lot of time in the last year working with Seam + Facelets (which requires JSF) + [MyFaces, Tomahawk, Richfaces + Ajax4JSF (now combined), etc...]. The programming model of Seam, that of using annotations to express dependencies is its most compelling feature. The business of tracing each framework component and working out integration issues is a nightmare that gets worse with each release of Seam (1.1 -> 1.2 -> 2.0) and/or one of the companion frameworks listed above and/or JBoss application server. And you can be sure that this will only get worse if/when Seam tries to become web beans forcing recoding of Seam applications that want to move to the web beans model because let's face it, the annotations are completely different in web beans.
Grails appears to be full stack in the sense that it just provides 'all the parts' (i.e. ORM, scaffolding, tags, code generation, etc.). If each of Grails constituent parts works seamlessly (no pun intended) with each other, then this would be a nice improvement over the current Seam experience. I like the fact that I can select which javascript library to use in Grails.
I agree that there are good reasons to be lazy and in that spirit I claim that working out companion framework integration is of no value to the developer (i.e. framework user/consumer). Part of the pitch of a good framework is high leverage / better productivity / no need to change code as the framework version numbers increase.
I'm tired of unexpected surprises from my frameworks. It's well past time to look at full-stack open-source frameworks like Grails, Rails, etc. IntelliJ IDEA already has good plugins for working with Grails, Rails + ruby, GWT, etc. Let's face it our bosses / clients aren't interested in paying us to work out why framework A won't play nice with a feature in framework B.
|
|
|
Message #243043
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
one word (spring)
Grails in fact uses Spring under the covers. Would be nice if there were more spring integration points exposed, especially with AOP and web flow -- though the first thing grails has to tackle is having documentation that isn't complete crap when it's even there at all.
|
|
|
Message #243051
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Re: one word (spring)
Grails in fact uses Spring under the covers. Would be nice if there were more spring integration points exposed, especially with AOP and web flow.
There are already a couple of integration points. Also, there is a nice integration between Grails and web flow. The complete flow can be described in Groovy (using Builders), so no more XML. See: http://grails.codehaus.org/WebFlow
The first thing grails has to tackle is having documentation that isn't complete crap when it's even there at all.
There are some books about Groovy and Grails. "The Definitive Guide to Grails (aPress)" is still a very good description of Grails and it's concepts, but it is not consistent with the current release. The book is currently being updated to be consistent with Grails 1.0.
The wiki based documentation is not bad and pretty complete. Also Graeme Rocher has published a first version of a reference manual that is available here:
http://grails.org/doc/RC1/
Overall I think Groovy and Grails are great for Java, because they make the simple things simple (using DRY, convention of configuration..), but have a strong and stable foundation (Java like syntax, allow to mix Groovy and Java, Hibernate, Spring, Sitemesh, ..).
Stephan Albers
http://www.jcatalog.com/
|
|
|
Message #243672
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Re: A Grails Convert ...
I agree. Grails is a pretty cool framework that rivals RoR for rapid development. Being able to reuse much of my existing Java code and ability to deploy as a war file are clear advantages over RoR to me.
Great stuff (uninspiring name aside).
|
|
|
| New content on TheServerSide.comNew content on TheServerSide.comNew content on TheServerSide.com |
|
|
Reza Rahman explores the features of the proposed JSR 299, Contexts and Dependency Injection for Java EE (CDI). When approved, it promises to be a key feature of Java EE 6.
(November 2, Article)
SAML is an XML-based standard for exchanging authentication and authorization data between security domains. The single most important problem that SAML was created to solve is the Web browser Single Sign-On problem. Many organizations are debating whether to stay with version 1.1 or move to 2.0. This article makes observations about both options.
(September 28, Article)
Joe Ottinger takes a look at how people learn, and applies it to the practice of programming. He notes that understanding how people learn is an essential part of working in a programming team.
(September 22, Article)
Stephen Maryka gave us an article about the Asynchronous Web and posed a number of questions that get examined like an approach to delivering Asynchronous Web capabilities through extensions to existing Java EE technologies.
(July 14, Article)
JavaServer Faces Flex goal is to provide users capability in creating standard Flex components, part of flexSDK which is open sourced through MPL license, as normal JSF components. This article by Ji Hoon Kim will provide an overview of creating a simple multilingual JSF page consisting of JSF Flex tags.
(June 29, Article)
In this session Jeff explores the key characteristics of successful SOA projects. He covers some of the patterns, and anti-patterns, tool sets, and strategies that he himself learned the hard way. Last, he provides a strategy and blueprint for achieving a high likelihood of success in your SOA project.
(June 23, Tech Talk)
Ari Zilka, CTO of Terracotta, Inc., talks about the new features in Terracotta 3.1, announced during JavaOne and available now.
(June 15, Tech Talk)
In this Tech Talk, Josh Long explores an integration challenge using Spring Integration and walks through the implementation, employing and expanding on the basic patterns of Enterprise Application Integration to tie together components into a function integration solution, and then demonstrates how Spring Integration helps address the integration requirements.
(June 15, Tech Talk)
In this Tech Talk, David Geary teaches you: The basics of Google Web Toolkit; How to implement Ajax-enabled applications in Java; Internationalization; Hooking into the browser history mechanism; Remote procedure calls.
(June 4, Tech Talk)
Jon Kern discusses the best architecture/technical solutions and ensure that they are repeated by all developers. By tackling the architecture up-front in a serial manner, subsequent parallel development will be much more manageable and predictable.
(May 28, Tech Talk)
This keynote describes the frustrations of modern knowledge workers in their quest to actually get some work done, and solutions for how to guard yourself against all those distractions. Neal Ford talks about environments, coding, acceleration, automation, and avoiding repetition as ways to defeat the misguided attempts to sap your ability to produce good work.
(May 26, Tech Talk)
Gil demonstrates how new, aggressive uses of already abundant compute capacity by common applications offer competitive value for application designers.
(May 21, Tech Talk)
Chris Keene introduces WaveMaker as a new way to automate the ability to generate Hibernate classes in order to more quickly bring OR mapping into an application.
(May 19, Article)
In this session Nati Shalom demonstrates how to take a standard Java EE web application and scale it out or down dynamically without changes to the application code. Seeing as most web applications are over-provisioned to meet infrequent peak loads, this is a dramatic change because it enables growing your application as needed, when needed, without paying for unutilized resources.
(May 19, Tech Talk)
Mastering EJB was one of the original and most influential EJB books in the industry. Mastering EJB III now returns with two new expert co-authors, updated for EJB 2.1 and 30% new chapters including security, integration, best practices, open source, and more.
(Book PDF Download)
The Application Server Matrix is a detailed listing of J2EE vendors and their application server products, with information on latest version numbers, J2EE spec support and licensing, pricing, platform support, and links to product downloads and reviews.
(Application Server Comparison Matrix)
|
|
