Grails Developers are the ones who all helped in making the open source web application framework Grails a reality. This was known as “Groovy on Rails” previously.What were the Grails developers trying to accomplish here though? Well Grails was developed with a quite a number of things in mind. Some of the major goals included:
• Providing sample applications which would display the frameworks power
• Using previous Java technologies such as hibernate and spring in a consistent yet simple interface
• Having both easy to use and powerful templates
• Having a dynamic tag library so that web page components can easily be created
• Having great Ajax support that can be easily extended or customized
• Providing both a powerful and persistent framework
• Providing a highly productive web framework to work on the Java platform
• Reduction in confusion and promoting easy learning on a consistent framework
• Providing documentation to users for parts of the framework which are relevant
• Providing a comprehensive development mode which should include the automatic reload of resources as well as a web server
When Grails was being designed the grails developers aimed for an easy to learn design which would also be very extensive and an easy way to develop applications. Grails was needed to have just the right amount of balance between very powerful features as well as consistency. Grails was also designed to be very productive. There are three properties Grails has that make it more productive than other tradition Java web frameworks. These include:
A ready to use environment for development
With the traditional Java development environments the responsibility of assembling the development units and this can be a very tedious task. Grails on the other hand comes with a development environment that incorporates a webserver so that the developer will be able to get started without any delays. Grails also prepares the web environment automatically for deployment and all necessary libraries are included in the Grails distribution.
No XML configuration is necessary
When a developer is going to create web applications using Java this involves configuring both frameworks and environments before and during the development. XML was happily welcomed before as initially it was seen to provide much greater consistency when developing applications. Recently though it has been found that XML can be very tedious when setting up an environment. This takes away a lot of productivity time from the developers as they may need to spend some time in understanding and maintaining the configuration as the application grows. With grails the need to add any XML configuration has been taken away.
Functionality is available via mixins
What is a mixin? This is a method that is added to class. These dynamic methods will allow the developer to now perform all needed operations without having to extend the base classes’orimplement interfaces.
With grails,developers have ensured that dynamic methods will be provided based on the type of class. An example of this is a method with automates the process of finding, deleting and saving.