Have you seen the comments at http://grails.org/blog/view/graemerocher/Grails+2.0.2+Released! ?

[Dean Del Ponte-2]

I wanted to read the grails-2.0.2 release notes and a google search brought me to http://grails.org/blog/view/graemerocher/Grails+2.0.2+Released!

I was a bit surprised to see the two negative comments posted there.

I successfully upgraded a non-trivial application from 2.0.1 to 2.0.2 without incident.

Are the comments posted at http://grails.org/blog/view/graemerocher/Grails+2.0.2+Released! legitimate ones?

Just curious because I didn't see anything in the mailing list.

I've pasted their comments below:

Version 2.0.2 neither start! 
Version 2.0.1 have very big bug in validation of numeric fileds !
How is possible!! This is alpha softwares not ready for pruduction!!
I had very big disappointment for your software, i will never use for my future project. 
Test your software before publish it!!!

Mar 30, 2012 05:03 AM gigi_igig

Just tried 2.0.2 and this [core?] functionality stopped working.

MyClass myInstance = new MyClass(field1: val1, field2: val2).save(insert:true)

if field1 or field2 are hasMany relationships, or simple hasOne relationships then the values are no longer set.  it quetlly fails and doesn't establish the relationship
.

[Ingo Wiarda]

The second comment probably refers to a known issue
http://jira.grails.org/browse/GRAILS-8972

(which for the time prevents me from upgrading from 2.0.1 to 2.0.2)

Ingo

On 30.03.2012 16:10, Dean Del Ponte wrote:

I wanted to read the grails-2.0.2 release notes and a google search brought me to http://grails.org/blog/view/graemerocher/Grails+2.0.2+Released!

I was a bit surprised to see the two negative comments posted there.

I successfully upgraded a non-trivial application from 2.0.1 to 2.0.2 without incident.

Are the comments posted at http://grails.org/blog/view/graemerocher/Grails+2.0.2+Released! legitimate ones?

Just curious because I didn't see anything in the mailing list.

I've pasted their comments below:

Version 2.0.2 neither start! 
Version 2.0.1 have very big bug in validation of numeric fileds !
How is possible!! This is alpha softwares not ready for pruduction!!
I had very big disappointment for your software, i will never use for my future project. 
Test your software before publish it!!!

Mar 30, 2012 05:03 AM gigi_igig

Just tried 2.0.2 and this [core?] functionality stopped working.

MyClass myInstance = new MyClass(field1: val1, field2: val2).save(insert:true)

if field1 or field2 are hasMany relationships, or simple hasOne relationships then the values are no longer set.  it quetlly fails and doesn't establish the relationship
.

[Graeme Rocher-4]

I believe the two problems relate to 2 issues with Grails 2.0.2:

a) One is http://jira.grails.org/browse/GRAILS-8972 which relates to
the changes to increase security by providing implicit whitelists. The
workaround is to specify bindable:true

b) We upgraded to Gradle 1.0 m9 which changed the structure of the
directories in the 'lib' directory. The IDEs (STS and Intellij) are
having trouble running Grails applications due to this change. This is
fixed in STS nightly snapshot. A workaround is to run the commands
from the command line instead of the IDE

Apologies to everyone for the inconvenience

Cheers
Graeme

On Fri, Mar 30, 2012 at 4:22 PM, Ingo Wiarda <[hidden email]> wrote:

> The second comment probably refers to a known issue
> http://jira.grails.org/browse/GRAILS-8972
>
> (which for the time prevents me from upgrading from 2.0.1 to 2.0.2)
>
> Ingo
>
>
> On 30.03.2012 16:10, Dean Del Ponte wrote:
>
> I wanted to read the grails-2.0.2 release notes and a google search brought
> me to http://grails.org/blog/view/graemerocher/Grails+2.0.2+Released!
>
> I was a bit surprised to see the two negative comments posted there.
>
> I successfully upgraded a non-trivial application from 2.0.1 to 2.0.2
> without incident.
>
> Are the comments posted
> at http://grails.org/blog/view/graemerocher/Grails+2.0.2+Released!
> legitimate ones?
>
> Just curious because I didn't see anything in the mailing list.
>
> I've pasted their comments below:
>
>
> Version 2.0.2 neither start!
> Version 2.0.1 have very big bug in validation of numeric fileds !
> How is possible!! This is alpha softwares not ready for pruduction!!
> I had very big disappointment for your software, i will never use for my
> future project.
> Test your software before publish it!!!
> Mar 30, 2012 05:03 AM gigi_igig
>
>
> Just tried 2.0.2 and this [core?] functionality stopped working.
>
> MyClass myInstance = new MyClass(field1: val1, field2:
> val2).save(insert:true)
>
> if field1 or field2 are hasMany relationships, or simple hasOne
> relationships then the values are no longer set.  it quetlly fails and
> doesn't establish the relationship
> .
>
>

--
Graeme Rocher
Grails Project Lead
SpringSource - A Division of VMware
http://www.springsource.com

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[jcam]

Hello,
I think the comment: 'Version 2.0.1 have very big bug in validation of numeric fileds !' is refering to a bug which I experienced too.
To reproduce it, create a new domain class like:

package com.mytest

class Person {
        String name
        Integer age
       
    static constraints = {
    }
}

then run grails command: grails generate-all com.mytest.Person
run application and use IE to create a new instance of Person using the controller generated. Fill the age field with no numeric value, eg: 'hello'
the application crashes when run action save() in instruction:
def personInstance = new Person(params)
Same behaviour occurs when you have a person instance created and you are going to change age value filling it with a no numeric value. Then fails on update() action in "personInstance.properties = params" instruction.

These errors does not happen when you use Chrome, because chrome parses the numeric field before to submit the form. I think it's supporting HTML5 tag <input type="number" .../> and IE is no supporting it.

Regards,

Jcam.