Ok thanks!
Mario
2016-04-25 19:23 GMT+02:00 John Smiljanic :
> Two separate compilations. One for the traits and transforms (framework
> code). The second for the user scripts that are transformed to dynamically
> implement the trait.
>
> On Apr 22, 2016, at 01:33, Mario Garcia wrote:
>
> Nice
You're welcome :)
On 25 Apr 2016 20:05, "Rick Venutolo" wrote:
> I had not thought to use that constructor. Thank you!
>
> On Mon, Apr 25, 2016 at 5:01 AM, Mario Garcia
> wrote:
>
>> Although I think It should be better to discuss this in the Grails
>> mailing list (they sure have much more expe
I had not thought to use that constructor. Thank you!
On Mon, Apr 25, 2016 at 5:01 AM, Mario Garcia wrote:
> Although I think It should be better to discuss this in the Grails mailing
> list (they sure have much more experience in Spring+Groovy) I have done a
> little test in a Grails app with a
Two separate compilations. One for the traits and transforms (framework code).
The second for the user scripts that are transformed to dynamically
implement the trait.
> On Apr 22, 2016, at 01:33, Mario Garcia wrote:
>
> Nice :)
>
> Just to get this straight, you compiled the traits first an
Although I think It should be better to discuss this in the Grails mailing
list (they sure have much more experience in Spring+Groovy) I have done a
little test in a Grails app with an immutable (@Immutable) bean:
package a.b.c
@Immutable
class Pagination {
Integer max
}
myBean(a.b.c.Paginati
