Tuesday, December 29, 2009

Spring Integration and Apache Camel


Spring Integration and Apache Camel are open source frameworks providing a simpler solution for the Integration problems in the enterprise, to quote from their respective websites:

Apache Camel -

Apache Camel is a powerful open source integration framework based on known Enterprise Integration Patterns with powerful Bean Integration.

Spring Integration -
It provides an extension of the Spring programming model to support the well-known Enterprise Integration Patterns while building on the Spring Framework's existing support for enterprise integration.

Essentially Spring Integration and Apache Camel enable applications to integrate with other systems.

This article seeks to provide an implementation for an integration problem using both Spring Integration and Apache Camel. The objective is to show how easy it is to use these frameworks for a fairly complicated integration problem and to recommend either of these great products for your next Integration challenge.


To illustrate the use of these frameworks consider a simple integration scenario, described using EIP terminology:


The application needs to get a "Report" by aggregating "Sections" from a Section XML over http service. Each request for Report consists of a set of request for sections – in this specific example there are requests for three sections, the header, body and footer. The XML over http service returns a Section for the Section Request. The responses need to be aggregated into a single report. A sample test for this scenario is of the following type:

        ReportGenerator reportGenerator = reportGeneratorFactory.createReportGenerator();
List<SectionRequest> sectionRequests = new ArrayList<SectionRequest>();

String entityId="A Company";

sectionRequests.add(new SectionRequest(entityId,"header"));
sectionRequests.add(new SectionRequest(entityId,"body"));
sectionRequests.add(new SectionRequest(entityId,"footer"));

ReportRequest reportRequest = new ReportRequest(sectionRequests);

Report report = reportGenerator.generateReport(reportRequest);
List<Section> sectionOfReport = report.getSections();
assertEquals(3, sectionOfReport.size());

The “ReportGenerator” is the messaging gateway, hiding the details of the underlying messaging infrastructure and in this specific case also the integration API – Apache Camel or Spring Integration. To start with, let us implement a solution to this integration problem using Spring Integration as the Framework, followed by Apache Camel. The complete working code using Spring Integration and Apache Camel is also available with the article.


Solution Using Spring Integration:

The Gateway component is easily configured using the following entry in the Spring Configuration. Internally Spring Integration uses AOP to hook up a component which routes the requests from an internal input channel and waits for the response in the response channel.

<si:gateway default-reply-channel="exit" default-request-channel="enter" id="reportGenerator" service-interface="org.bk.report.ReportGenerator">

The component to Split the Input Report Request to Section Request is fairly straightforward:
public class SectionRequestSplitter {    
public List split(ReportRequest reportRequest){
return reportRequest.getSectionRequests();

and to hook this splitter with Spring Integration:
<bean class="org.bk.report.common.SectionRequestSplitter" id="sectionRequestSplitterBean">

<si:splitter id="sectionRequestSplitter" input-channel="enter" method="split" output-channel="sectionRequestToXMLChannel" ref="sectionRequestSplitterBean">

Next, to transform the Section Request to an XML format - The component is the following:
public class SectionRequestToXMLTransformer {
public String transform(SectionRequest sectionRequest){
//this needs to be optimized...purely for demonstration of the concept
String sectionRequestAsString = "<section><meta><entityId>" + sectionRequest.getEntityId()
+ "</entityId><sectionName>" + sectionRequest.getSectionId()
+ "</sectionName></meta></section>";

return sectionRequestAsString;

and is hooked up in the Spring Integration configuration file in the following way:
<bean id="sectionRequestToXMLBean" class="org.bk.report.common.SectionRequestToXMLTransformer"/>
<si:transformer input-channel="sectionRequestToXMLChannel" ref="sectionRequestToXMLBean" method="transform" output-channel="sectionRequestChannel"/>
To send an XML over http request using the Section Request XML to a section Service:
<http:outbound-gateway id="httpHeaderGateway"
request-channel="sectionRequestChannel" reply-channel="sectionResponseChannel"
default-url="${sectionBaseURL}/section" extract-request-payload="true"
charset="UTF-8" request-timeout="1200" />

To transform the Section Response XML to a Section Object - The component is the following:
public class SectionResponseXMLToSectionTransformer {
public Section transform(String sectionXML) {
SAXReader saxReader = new SAXReader();
Document document;
String sectionName = "";
String entityId = "";
try {
document = saxReader.read(new StringReader(sectionXML));

sectionName = document
entityId = document.selectSingleNode("/section/meta/entityId")
} catch (DocumentException e) {
return new Section(entityId, sectionName, sectionXML);
and is hooked up in the Spring Integration configuration file in the following way:
<bean id="sectionResponseXMLToSectionBean" class="org.bk.report.common.SectionResponseXMLToSectionTransformer" />
<si:transformer input-channel="sectionXMLResponseChannel"
ref="sectionResponseXMLToSectionBean" method="transform" output-channel="sectionResponseChannel" />

To aggregate the Sections together into a report, the component is the following::
public class SectionResponseAggregator {

public Report aggregate(List<Section> sections) {
return new Report(sections);


and is hooked up in the Spring Integration configuration file in the following way:
<bean id="sectionResponseAggregator" class="org.bk.report.common.SectionResponseAggregator"/>
<si:aggregator input-channel="sectionResponseChannel" output-channel="exit" ref="sectionResponseAggregator" method="aggregate"/>

This completes the Spring Integration implementation for this Integration Problem. The following is the complete Spring Integration configuration file:

<beans xmlns="http://www.springframework.org/schema/beans"
xmlns:context="http://www.springframework.org/schema/context" xmlns:si="http://www.springframework.org/schema/integration"
xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd
http://www.springframework.org/schema/integration http://www.springframework.org/schema/integration/spring-integration-1.0.xsd
http://www.springframework.org/schema/context http://www.springframework.org/schema/context/spring-context-2.5.xsd
http://www.springframework.org/schema/integration/http http://www.springframework.org/schema/integration/http/spring-integration-http-1.0.xsd

<context:property-placeholder />
<si:channel id="enter" />

<si:channel id="exit" />

<si:gateway id="reportGenerator" default-request-channel="enter"
default-reply-channel="exit" service-interface="org.bk.report.ReportGenerator" />

<si:channel id="sectionRequestToXMLChannel" />
<si:splitter id="sectionRequestSplitter" input-channel="enter"
ref="sectionRequestSplitterBean" method="split" output-channel="sectionRequestToXMLChannel" />

<si:channel id="sectionRequestChannel" />
<si:transformer input-channel="sectionRequestToXMLChannel"
ref="sectionRequestToXMLBean" method="transform" output-channel="sectionRequestChannel" />

<si:channel id="sectionXMLResponseChannel" />
<http:outbound-gateway id="httpHeaderGateway"
request-channel="sectionRequestChannel" reply-channel="sectionXMLResponseChannel"
default-url="${sectionBaseURL}/section" extract-request-payload="true"
charset="UTF-8" request-timeout="1200" />

<si:channel id="sectionResponseChannel" />
<si:transformer input-channel="sectionXMLResponseChannel"
ref="sectionResponseXMLToSectionBean" method="transform" output-channel="sectionResponseChannel" />

<si:aggregator input-channel="sectionResponseChannel"
output-channel="exit" ref="sectionResponseAggregator" method="aggregate" />

<bean id="sectionRequestSplitterBean" class="org.bk.report.common.SectionRequestSplitter" />
<bean id="sectionRequestToXMLBean" class="org.bk.report.common.SectionRequestToXMLTransformer" />
<bean id="sectionResponseXMLToSectionBean" class="org.bk.report.common.SectionResponseXMLToSectionTransformer" />
<bean id="sectionResponseAggregator" class="org.bk.report.common.SectionResponseAggregator" />



A working sample is provided with the article(Download, extract and run "mvn test")


Solution using Apache Camel:

Apache Camel allows the route to be defined using multiple DSL implementations – Java DSL, Scala DSL and an XML based DSL. The recommended approach is to use Spring CamelContext as a runtime and the Java DSL for route development. The following is to build the Spring Camel Context:

<camelContext id="camel" xmlns="http://camel.apache.org/schema/spring">
<template id="camelTemplate" />
<routeBuilder ref="routeBuilder"/>

The route is configured by the Java based DSL:
public class CamelRouteBuilder extends RouteBuilder {
private String serviceURL;

public void configure() throws Exception {

.split().method("sectionRequestSplitterBean", "split")
.aggregationStrategy(new ReportAggregationStrategy())
.transform().method("sectionRequestToXMLBean", "transform")
.transform().method("sectionResponseXMLToSectionBean", "transform");

public void setServiceURL(String serviceURL) {
this.serviceURL = serviceURL;
Apache Camel does not provide an out of the box Message Gateway feature, however it is fairly easy to create a wrapper component that can hide the underlying details in the following way:
public class CamelReportGenerator implements ReportGenerator {
private ProducerTemplate producer;

public Report generateReport(ReportRequest reportRequest) {
Report report = (Report)producer.requestBody("direct:start", reportRequest);
return report;

public void setProducer(ProducerTemplate producer) {
this.producer = producer;

This is a simple wrapper around Apache Camel's Producer Template which is essentially a handle to Apache Camel's route for this specific integration problem. The component to Split the Input Report Request to Section Request is exactly same as Spring Integration component:
public class SectionRequestSplitter {

public List<SectionRequest> split(ReportRequest reportRequest){
return reportRequest.getSectionRequests();

To hook the component with Apache Camel:
<bean id="sectionRequestSplitterBean" class="org.bk.report.si.SectionRequestSplitter" />

.split().method("sectionRequestSplitterBean", "split")
Next to transform the Section Request to an XML format, again this is exactly same as the implementation for Spring Integration, with hook being provided in the following manner:
.transform().method("sectionRequestToXMLBean", "transform")
To send an XML over http request using the Section Request XML to a section Service:
.transform().method("sectionRequestToXMLBean", "transform")
To transform the Section Response XML to a Section object, the component is exactly same as the one used with Spring Integration, with the following highlighted hook in the Camel route:
.transform().method("sectionResponseXMLToSectionBean", "transform");

To aggregate the Section responses together into a report, the component is a bit more complicated than Spring Integration. Apache Camel supports a Scatter/Gather pattern using a route of the following type:
.split().method("sectionRequestSplitterBean", "split")
.aggregationStrategy(new ReportAggregationStrategy())
with an aggregation strategy being passed on to the Splitter, the aggregation strategy implementation is the following:
public class ReportAggregationStrategy implements AggregationStrategy {
public Exchange aggregate(Exchange oldExchange, Exchange newExchange) {
if (oldExchange == null) {
Section section = newExchange.getIn().getBody(Section.class);
Report report = new Report();
return newExchange;

Report report = oldExchange.getIn().getBody(Report.class);
Section section = newExchange.getIn().getBody(Section.class);
return oldExchange;

This completes the Apache Camel based implementation. A working sample for Camel is provided with the article - just download, extract and run "mvn test".


Spring Integration and Apache Camel provide a simple and clean approach for the Integration problems in a typical enterprise. They are lightweight frameworks – Spring Integration builds on top of Spring portfolio and extends the familiar programming model for the Integration domain and is easy to pick up, Apache camel provides a good Java based DSL and integrates well with Spring Core, with a fairly gentle learning curve. The article does not recommend one product over the other but encourages the reader to evaluate and learn from both these frameworks.


Spring Integration Website: http://www.springsource.org/spring-integration
Apache Camel Website: http://camel.apache.org/
Spring Integration Reference: http://static.springsource.org/spring-integration/reference/htmlsingle/spring-integration-reference.html
Apache Camel User Guide: http://camel.apache.org/user-guide.html
Plug for my blog: http://biju-allandsundry.blogspot.com/
Spring Integration Implementation for the Problem: http://sites.google.com/site/bijukunjummen/reportgenerator-springintegration.zip
Apache Camel Implementation for the Problem: http://sites.google.com/site/bijukunjummen/reportgenerator-camel.zip

Monday, December 14, 2009

Lumosity and Physical Exercise

I am a subscriber of Lumosity, it is a website which has a wonderful set of small games designed to improve and test memory, attention and other cognitive functions.

I have found that whenever I exercise a bit, I get a jump in my scores!!

I know this is well known, but experiencing this for myself vs just reading about it are two different things. Now that I KNOW that exercise helps, this is a nice little feedback loop for me to pull myself up these winter days and hit the Gym more often

Friday, December 4, 2009

Ubuntu: Problem during "gem install" - /usr/bin/ruby1.8 extconf.rb

If you get this when installing sqlite3-ruby:
biju@ubhome:~$ sudo gem install sqlite3-ruby
Building native extensions.  This could take a while...
ERROR:  Error installing sqlite3-ruby:
 ERROR: Failed to build gem native extension.

/usr/bin/ruby1.8 extconf.rb
extconf.rb:1:in `require': no such file to load -- mkmf (LoadError)
 from extconf.rb:1

Gem files will remain installed in /var/lib/gems/1.8/gems/sqlite3-ruby-1.2.5 for inspection.
Results logged to /var/lib/gems/1.8/gems/sqlite3-ruby-1.2.5/ext/sqlite3_api/gem_make.out

Then solution gleaned from Google is to run:
biju@ubhome:~$ sudo apt-get install ruby1.8-dev

If it says:
biju@ubhome:~/notes$ sudo gem install sqlite3-ruby
Building native extensions.  This could take a while...
ERROR:  Error installing sqlite3-ruby:
 ERROR: Failed to build gem native extension.

/usr/bin/ruby1.8 extconf.rb
checking for fdatasync() in -lrt... yes
checking for sqlite3.h... no

Then solution is to run:
biju@ubhome:~/notes$ sudo apt-get install libsqlite3-dev

"sudo gem install sqlite3-ruby" should just run with these libraries in place.

If you see the following while starting the rails application:
./script/../config/../vendor/rails/railties/lib/initializer.rb:259:in `require_frameworks': no such file to load -- openssl (RuntimeError)
 from ./script/../config/../vendor/rails/railties/lib/initializer.rb:133:in `process'
 from ./script/../config/../vendor/rails/railties/lib/initializer.rb:112:in `send'
 from ./script/../config/../vendor/rails/railties/lib/initializer.rb:112:in `run'

then run:
sudo apt-get install libopenssl-ruby

Saturday, October 31, 2009

Scala Maven projects with multiple source folders

I had a need on a recent scala based maven project to be able to support multiple source folders - to hold the scala and java source and tests separately."Build Helper" Maven plugin perfectly fit this need, the following is a sample pom.xml configured using this plugin:

There are two sources - src/main/java holding the java code, and src/main/scala holding the scala code
and two test sources - src/test/java, src/test/scala.

<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0"
     xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">


        <name>Scala-tools Maven2 Repository</name>
        <name>Scala-tools Maven2 Repository</name>

Saturday, August 29, 2009

Spring Web Services - How to - Article contributed to Javalobby - http://java.dzone.com/articles/spring-ws-how

Spring Webservices encourages a contract first, message oriented approach to creating Webservices. The underlying details are completely under developer control starting from the contract to the marshalling/unmarshalling details to the endpoint handling the request.

Let us start by an example of a simple service to expose as a webservice - call it the MemberService. MemberService exposes one operation “Get Member Details” which returns the details of a member/person, given an identifier.

Creating the contract:

The Contract/WSDL for this service is fairly simple. Let us start by defining the messages and type :

01.<xsd:schema targetNamespace="http://bk.org/memberservice/" elementFormDefault="qualified">
02. <xsd:complexType name="MemberDetailType">
03. <xsd:sequence>
04. <xsd:element name="name" type="xsd:string" />
05. <xsd:element name="phone" type="xsd:string" />
06. <xsd:element name="city" type="xsd:string" />
07. <xsd:element name="state" type="xsd:string" />
08. xsd:sequence>
09. xsd:complexType>
10. <xsd:element name="MemberDetailsRequest">
11. <xsd:complexType>
12. <xsd:sequence>
13. <xsd:element name="id" type="xsd:string" />
14. xsd:sequence>
15. xsd:complexType>
16. xsd:element>
17. <xsd:element name="MemberDetailsResponse">
18. <xsd:complexType>
19. <xsd:sequence>
20. <xsd:element name="memberdetail" type="ms:MemberDetailType" />
21. xsd:sequence>
22. xsd:complexType>
23. xsd:element>

MemberRequest message comprises of an id to represent the requested members identifier

MemberResponse message comprises of MemberDetail type to represent the details of a member.

A sample payload over the wire would look like this:

1.xml version="1.0"?>
2.<ms:MemberDetailsRequest xmlns:ms="http://bk.org/memberservice/">
3. <ms:id>SAMPLEms:id>

and a sample response:

1.<ms:MemberDetailsResponse xmlns:ms="http://bk.org/memberservice/">
2. <ms:memberdetail>
3. <ms:name>testnamems:name>
4. <ms:city>testcityms:city>
5. <ms:phone>testphonems:phone>
6. <ms:state>teststatems:state>
7. ms:memberdetail>

The sample request and response can be easily generated by using a tool like SOAP UI –


Creating an Endpoint:

A Spring-WS endpoint processes the XML message and produces the XML response. Spring provides different Endpoints based on how the XML is to be handled. If you wish to handle raw xml you have the option of implementing AbstractDom4jPayloadEndpoint, AbstractDomPayloadEndpoint, AbstractJDomPayloadEndpoint etc, based on how the raw xml needs to be handled. If you wish to handle the XML message as an object representation then you can implement the AbstractMarshallingPayloadEndpoint, which is what I will be using for this example along with JIBX as the XML binding framework for its ease of use and performance.

01.package org.bk.memberservice.endpoint;
03.import org.bk.memberservice.message.MemberDetailsRequest;
04.import org.bk.memberservice.message.MemberDetailsResponse;
05.import org.bk.memberservice.service.MemberManager;
06.import org.bk.memberservice.types.MemberDetail;
07.import org.springframework.ws.server.endpoint.AbstractMarshallingPayloadEndpoint;
09.public class GetMemberDetailsEndpoint extends
10. AbstractMarshallingPayloadEndpoint {
12. private MemberManager memberManager;
14. protected Object invokeInternal(Object requestObject) throws Exception {
15. MemberDetailsRequest request = (MemberDetailsRequest) requestObject;
16. MemberDetail memberDetail = memberManager.getMemberDetails(request
17. .getId());
18. MemberDetailsResponse response = new MemberDetailsResponse(memberDetail);
19. return response;
21. }
23. public void setMemberManager(MemberManager memberManager) {
24. this.memberManager = memberManager;
25. }
The structure of the Endpoint is very simple, it takes an Object which can be cast to MemberDetailsRequest a holder for the request, and the response is returned as an instance of MemberDetailsResponse, a holder for the response details.

Writing the Object/XML binding:

So we now have the endpoint to process the take in the request Message, process it and respond. The only missing piece is how to transform the raw request xml over the wire to the MemberDetailsRequest object, and on the way back to transform the MemberDetailsResponse object back to XML. This is where Springs Object/XML mapping support comes in. Spring Object/XML mapper provides a simple abstraction over the popular Java XML binding stacks like JAXB, Castor, JiBX, Xstream. In the current example, we will start by defining the binding file for JiBX:

01.xml version="1.0" encoding="UTF-8"?>
03. <mapping name="MemberDetailsRequest"
04. class="org.bk.memberservice.message.MemberDetailsRequest">
05. <namespace prefix="ms" uri="http://bk.org/memberservice/" default="all"/>
06. <value name="id" field="id" />
07. mapping>
09. <mapping name="MemberDetailsResponse"
10. class="org.bk.memberservice.message.MemberDetailsResponse">
11. <namespace prefix="ms" uri="http://bk.org/memberservice/" default="all"/>
12. <structure name="memberdetail" field="memberDetail"
13. class="org.bk.memberservice.types.MemberDetail">
14. <value name="name" field="name" />
15. <value name="city" field="city" />
16. <value name="phone" field="phone" />
17. <value name="state" field="state" />
18. structure>
19. mapping>

JiBX requires a compile step with the above binding file, this is very easily wired using Maven as the build tool.

Putting it together:

So now all the pieces are in place -

To direct the request to the appropriate endpoint, Spring-WS requires a custom servlet to be set up:

02. <servlet-name>memberserviceservlet-name>
03. <servlet-class>org.springframework.ws.transport.http.MessageDispatcherServletservlet-class>
04. <init-param>
05. <param-name>contextConfigLocationparam-name>
06. <param-value>classpath:/applicationContext-memberservice.xmlparam-value>
07. init-param>
11. <servlet-name>memberserviceservlet-name>
12. <url-pattern>/services/*url-pattern>

This would direct all requests starting with serivces/* to be handled by Spring-WS.

The MessageDispatcherServlet would look for a Spring bean with id of “payloadMapping” to direct the incoming XML to an appropriate endpoint, for the example the bean entry is the following:

01.<bean id="payloadMapping"
02. class="org.springframework.ws.server.endpoint.mapping.PayloadRootQNameEndpointMapping">
03. <property name="endpointMap">
04. <map>
05. <entry key="{http://bk.org/memberservice/}MemberDetailsRequest"
06. value-ref="getMemberDetailsEndpoint" />
07. map>
08. property>

Essentially a request with MemberDetailsRequest as the element will be directed to getMemberDetailsEndpoint which is :

1. <bean id="getMemberDetailsEndpoint" class="org.bk.memberservice.endpoint.GetMemberDetailsEndpoint">
2. <property name="marshaller" ref="marshaller" />
3. <property name="unmarshaller" ref="unmarshaller" />
4. <property name="memberManager" ref="memberManager" />

The Endpoint needs the marshaller and unmarshaller to be injected to transform the request XML to request object and the response object to response XML. These are created as follows:

01. "marshaller" class="org.springframework.oxm.jibx.JibxMarshaller">
02. name="targetClass"
03. value="org.bk.memberservice.message.MemberDetailsResponse" />
06. "unmarshaller" class="org.springframework.oxm.jibx.JibxMarshaller">
07. name="targetClass"
08. value="org.bk.memberservice.message.MemberDetailsRequest" />

Exposing the Webservice WSDL:

Since the WSDL was created from scratch, to expose this pre-canned wsdl requires a bit more configuration with Spring:

1.<bean id="MemberDetailsRequest"
2. class="org.springframework.ws.wsdl.wsdl11.SimpleWsdl11Definition">
3. <property name="wsdl" value="classpath:/memberservice.wsdl" />

Now, when the request comes in for the URI /memberservice/MemberDetailsRequest.wsdl, Spring-WS would serve out the static memberservice.wsdl.

This completes the Webservice implementation. It can be further enhanced to handle the Exception scenarios, Security etc which is an exercise for another day.

The complete example can be run using the attached maven enabled code, which will download all dependencies, and can be run using the following command:

mvn jetty:run


Spring-WS provides a compelling way to create a webservice with a contract first approach. The amount of code appears extensive, however there is clean separation of the contract defined by the WSDL and the implementation, thus being able to change underlying implementation without affecting the contract.

Tuesday, May 19, 2009

Font configuration in Ubuntu Jaunty Jackalope

This is the font configuration that has worked extremely well for me in my Dell Inspiron laptop:

1. Font size of 9 across the board

2. Entries in ~/.fonts.conf file, based on the recommendations from the following post -

<match target="font">
<edit mode="assign" name="antialias">
<edit mode="assign" name="hinting">
<edit mode="assign" name="hintstyle">
<edit mode="assign" name="lcdfilter">
<edit mode="assign" name="rgba">

3. The fonts within firefox looked extremely tiny at the end of this exercise. This was improved by installing Microsoft Core fonts :
sudo apt-get install msttcorefonts gsfonts-x11

Thursday, January 1, 2009

Grails - Musings

I have long observed Grails passively, rejoiced that there is now a web framework in Java that does not require jumping through hoops to get a basic setup working. Free time has been a bit of a constraint through 2008, so I never got enough time to spend exploring Grails.
When I heard about the release of Grails 1.1 Beta 2, around Christmas time, I decided I had enough of a free time during the holidays to actually start learning Grails.

A good tutorial that I started following is a Grails Web Album tutorial by John Leach - It is a fairly complex application about creating an online photo album. I was easily able to follow the tutorial and at the end was amazed by how simple it was to create a working application. A great thing about the tutorial is that an equivalent Rails version is also available at John Leach's site, that allowed me to compare and contrast Rails with Grails. I am already fairly proficient in Rails, so one thing that stood out in Grails for me was that specifically for the Web Album application, all the image manipulation libraries were available right within Java, whereas the Rails version required using RMagick, which is fairly difficult to configure on a Windows XP box.
My conclusion is fairly simple - Both Grails and Rails are compelling Web frameworks, both have a fairly flat learning curve and the underlying languages(Groovy, Ruby) are delightful and fun to learn and use. I very much intend to continue exploring both Grails and Rails.