Domain constructor taking map of values fails to create associations and lists

Grails 2.0.2 introduces implicit white lists to increase security. Can you please set bindable:true on the properties that are not binding. See:

http://grails.org/doc/2.0.2/ref/Constraints/bindable.html

I hit this problem too. My case was something like this:

 
class Book {

  static hasOne [
    author: Author
  ]
}

in grails 2.0.1 the following constructor worked. new Book(author: myAuthor)

but that now breaks in 2.0.2

Another work around is to explicitly declare the property

class Book {

  Author author

  static hasOne [
    author: Author
  ]
}

You can also do:

class Book {

  static hasOne [
    author: Author
  ]

  static constraints = {
     author bindable:true
  }
}

Totally agree with John Hayward. We can not upgrade to Grails 2.0.2 until we know if this is a bug or not. This is a real breaking change.

It will be nice if this feature could be enabled or disabled globally with a configuration property like "grails.gorm.bindable"

Alberto/Mathieu - Yeah sorry, in retrospect it was too aggressive a change to make associations not bindable by default without "bindable: true". We will put out a quick 2.0.3 to correct the problem.

I can't bind Maps in Grails 2.0.3 with or without bindable:true. I have to explicitly set the map on the object. We are using the mongo plugin, so we use Maps frequently. Is there something else that I need to do?

@Dan, I found that we had the same problem on upgrading to grails 2.0.1 from 1.3.7. I think it is change in the implicit constructor of groovy actually, and not a grails specific problem.

@Brian and @Dan
I have the same problem here in 2.0.3. A lot of our unit tests depend on this behavior, and rewriting all of them (around 500) would be very timeconsuming.

        Customer customer = new Customer(
                payment: new Payment(
                        accountNumber: "1234567",
                        payer: new Person(
                                surname: "Payer"
                        )),
                person: new Person(
                        surname: "Person"
                )
        )

This works in Grails 1.3.x, but in Grails 2.0.3, the person is filled, but the payment is null. Changing the sequence doesn't have any effect, and the only difference so far I could find was that Person is a domain object, while Payment isn't.

However, I still have the same problem Dan has, and I don't think this bug is fixed. If there's any way I can help, or provide more information, please let me know.

I'm getting this with 2.0.3 as well. transient domain properties cannot be set in the Domain objects constructor. this is causing my app to null pointer unless i re-code how i construct domain objects. is there a workaround?

thanks.

@Trevor, take a look at this related reported bug:

http://jira.grails.org/browse/GRAILS-9098

Unfortunately it was marked as "won't fix", but I guess you can set your transient properties as bindable as a workaround.

I have still the same problem and the property isn't transient...

class FieldDefinition

def x = new FieldDefinition( fieldName: "quantity", fieldComperator: FieldComparator.GREATER, fieldValue: 3.0 )

will lead into that the x.fieldValue is null.
I'm using Grails 2.1.4 and java version "1.6.0_45"

Harald,

Your fieldValue is not statically typed. Only statically typed properties which are not transient and not static are bindable by default. In order for fieldValue to be bindable it needs to be configued with bindable: true, or you need to assign the value explicitly like this:

x.fieldValue = 3.0

First off all I'm impressed of the response time! Many thanks for it.
And you are right, after configuring the Object property as bindable true it was working.
Many thanks