Errata

Programming Grails

Errata for Programming Grails

Submit your own errata for this product.

The errata list is a list of errors and their corrections that were found after the product was released.

The following errata were submitted by our customers and have not yet been approved or disproved by the author or editor. They solely represent the opinion of the customer.

Color Key: Serious technical mistake Minor technical mistake Language or formatting error Typo Question Note Update

Version Location Description Submitted by Date Submitted
Printed Page 123
First paragraph underneath code snippet

"If you are integrating legacy code in a Grails applicaiton, [...]"

should be

"If you are integrating legacy code in a Grails application, [...]"

 Sascha Ritter  Nov 10, 2013 
Printed Page 39
First headline

"A nte about the work directory"

should be

"A note about the work directory"

 Sascha Ritter  Nov 10, 2013 
Printed Page 29
First paragraph underneath "Overload Your Operators"

"It's important that if you add an operator overload that it make sense [...]"

should be

"It's important that if you add an operator overload that it makes sense [...]"

 Sascha Ritter  Nov 10, 2013 
Printed Page 6
2nd paragraph

In the second paragraph: "and in this case, only the setName(), getCount(), and setCount() methods will be added"

The first method must be getName() instead of setName().

 Bilgehan Maraş  May 10, 2013 
PDF Page 37
1st paragraph/note - about "non-persistent domain classes"


The dialog/note on page 37 of Chapter 3: Persistence, just above the 'Data Validation' section, describes how one can achieve non-persistent domain classes.

It indicates:

"You may ask how to have non-persistent domain classes in your application, and the short answer is that you can?t."

Technically, this is incorrect - you can have a non-persistent domain class in your application under .../grails-app/domain, by specifying:

static mapWith = "none"

... in the domain class that is intended to be non-persistent. ( this is nice also, because: it still supports constraints, you don't need to artificially separate non-persistent domain business logic off into ../src/groovy, or any other workarounds as suggested in that section.

More info:

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

... this feature is currently undocumented:

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

 Corey Saltiel  Sep 30, 2012 
PDF Page 6
Top

"and in this case only the setName(), getCount(), and setCount() methods will be added"

should be

"and in this case only the getName(), getCount(), and setCount() methods will be added"

setName has just been explicitly added

 John Moore  May 16, 2012 
PDF Page 9
1st java code sample

The working java anonymous inner class example is missing a semi-colon in the interface (which I believe is supposed to be a Java interface, not a Groovy one):

interface Clickable {
void onClick()
}

It should use square brackets instead of squiggly brackets


interface Clickable {
void onClick();
}

 Ted Naleid  May 14, 2012