Oh maaaaaan..... what an idiot. That's a lesson in reading the stack trace carefully. Bad programmer.
On looking back at the last message, line 31 just had a loop qmEvents.get(i).getClass.getCanonicalName(); funnily enough as you suspected, the class name was not a LibraryQueueMemberEvent. It was a String from the database query return, which is what I was checking for before I came to the list, half-gone-mad.. Thiago, I am sorry to have wasted your time in the end as it was not a tapestry error. Noted, re nabble and eating stuff. I just stopped using a dedicated desktop mail user agent and nabble seems like a good tool for browsing. Might have to re-work that workflow because I remember reading stripped posts...frustrating thoughts...ah the karma Kind Regards, Chris -- View this message in context: http://tapestry.1045711.n5.nabble.com/3-days-of-ValueEncoder-ing-no-coercion-found-tp5720109p5720226.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
