id initialization on constructor when generator is assigned

Moving non-critical issues that aren't going to make it into 1.1 to 1.2

I think this is a clone of
http://jira.codehaus.org/browse/GRAILS-3431
or vice versa.

There is no scope / time to resolve these remaining lower priority issues for 1.2 so moving to 1.3

for 1.2 final only issues considered blocking will now be fixed

It seemed to me that this worked for Grails 2.0.0 and 2.0.1 but does not work for Grails 2.0.3 any more. Can anybody confirm that?

Dominik, it could be a problem related to GRAILS-8972 . Try adding "bindable:true" to id's constraint definition.

That seemed to be the problem. Thank you, Lari!

This is a minimal grails 2.0.3 example as per the description, with bindable:true on the String id. However id initialisation still does not work.

I tried it with 2.0.4 and it was not successful either.

Any help appreciated as this is causing us test harnesses pain for a framework with a lot of generated:assigned ids.

Probably related to the data binding changes. Jeff - please take a look

Just to add more information, I've tried again with 2.1.0.RC3 and no luck.

Attaching grails1984.zip which contains a 2.1.0.RC3 project. Bootstrap is creating instances of CurrencyRow and assigning an id as a constructor argument successfully.

Are there scenarios which do not work in 2.1.0.RC3?

It doesn't work when used within a controller or service. E.g. try adding a CurrencyRow using the CurrencyRowController of your example or add a method to the controller:

def testme() {
   def v = new CurrencyRow(id: "test", numericCode: 100)
   render "id: ${v.id}"
}

I see now why the behavior is different in a controller than it is in Bootstrap.

Will get this sorted out asap.

Thanks for the info.

I've written a small article with a temporary workaround for this bug: http://www.redcube.de/assigning-id-domain-objects-grails-via-constructor/

Try this way
def v = new CurrencyRow(numericCode: 100)
v.id="test"
or
def v = new CurrencyRow()
v.id="test"
v.numericCode=100

This is still an issue in 2.2.0. The only way to get the domain object created/stored successfully is to assign id separately from the constructor.

It works when you add the (undocumented?) constraint "bindable: true" to the id field:

class MyDomain {
    static constraints = {
        // allow binding of "id" attribute (e.g. in constructor or url parameters)
        id bindable: true
    }
}

FYI...

The bindable constraint is documented at http://grails.org/doc/latest/ref/Constraints/bindable.html and more details about secure data binding are noted at http://grails.org/doc/latest/guide/single.html#dataBinding.