SpringSource发布 Grails 1.2 最终版

jieforest

Named URL Mappings

Grails now supports named URL mappings and associated dynamic tags for view layer URL rewriting. For example:

name productDetail: "/showProduct/$productName/$flavor?" {
          controller = "product"
          action = "show"
      }

The above creates a named URL mapping called "productDetail" this can be linked to from the view with:

<linkroductDetail
       productName="licorice"
       flavor="strawberry">Strawberry Licorice</linkroductDetail>

jieforest

Better JSONBuilder

JSONBuilder has been re-written, better documented and improved in general. Rendering JSON responses is now as simple as:

render(contentType:"text/json") {
        categories = [ { a = "A" }, { b = "B" } ]
}

Which will produce:

{"categories":[ {"a":"A"} , {"b":"B"}] }

This is breaking change from previous versions of Grails, if you want backwards compatibility set grails.json.legacy.builder=true in Config.groovy

jieforest

Better Date parsing

If you submit a date from a <g:datePicker name="foo" /> tag, obtaining the Date object is now as simple as looking it up from the params object by name (eg. params.foo )

jieforest

Convenient, null safe converters in params and tag attributes

New convenience methods have been added to the params object and tag attrs objects that allow the easy, exception safe and null safe conversion of parameters to common types:

def total = params.int('total')

There are methods for all the common base types such as int@, @long@, @boolean and so on. There is a special converter called list that always returns a list for cases when dealing with one or many parameters of the same name:

def names = params.list('names')

jieforest

REST improvements

The <g:form> tag can now pass other methods beside POST and GET:

<g:form method="DELETE">

This works by creating a hidden field called _method. Now browser clients can also pass the X-HTTP-Method-Override HTTP header

jieforest

Project Documentation Engine

The same documentation engine that powers the Grails reference documentation is now available in your projects. Simply create your documentation inside the src/docs/ref and src/docs/guide directories of your project. See the Grails documentation source for an example.

The engine is also usable outside of Grails by adding the grails-docs dependency to your application (example in Gradle syntax):

compile group: 'org.grails', name: 'grails-docs', version:'1.2.0.RC1'

And using the provided Ant task:

ant.taskdef (name: 'docs', classname : 'grails.doc.ant.DocPublisherTask')
ant.docs(src:"src/docs", dest:"build/docs",
                properties:"src/docs/doc.properties")

jieforest

Zip-only plugin releases

If you prefer to use Git/Mercurial/etc. to version control your plugin you can now distribute only the zipped release of the plugin in the central repository and continue to manage the actual sources outside of SVN:

grails release-plugin --zipOnly

jieforest

Plugin Metadata

Every plugin Groovy source or GSP view is now annotated with a @GrailsPlugin annotation which describes the name and the version of the plugin that the source or view originates from. This adds additional capabilities to Grails in terms of the runtime discovery of plugin sources.

In addition, when releasing a plugin into the Grails central repository metadata is generated about the methods and properties added to Grails classes at runtime.

This metadata is put into the plugin.xml descriptor and can be read by IDEs and documentation engines.

If your plugin doesn't add methods at runtime you can skip the metadata generation process by doing:

grails release-plugin --skipMetadata

jieforest

formatNumber and formatDate taglib improvements

g:formatNumber and g:formatDate taglibs are now feature compatible with JSTL formatNumber and formatDate tags.

jieforest

Property Override Configuration Improvements

The Property Override mechanism has been improved to support non-String types and transactional services.

// Config.groovy
beans {
        someService {
                someProperty = new SomeObject()
        }
}