The stacktrace should tell you what line in your code the problem originated from, it just won't be the first thing the stacktrace shows you. Because there are so many layers in Groovy, it probably showed you a MissingMethodException or something because it was looking for a setLong method that accepted a String.
Whenever I get a stacktrace like that, I usually pick a unique
word from my packaging and search through the stacktrace for it. That way I can find the first line in
my code that caused the problem. For example if all my Groovy code is in
com.mcdonalds.burgerapp, I'll search the stacktrace for
mcdonalds.
[ October 22, 2008: Message edited by: Matthew Taylor ]