Re: 3 days of ValueEncoder-ing, no coercion found

2013-02-26 Thread Thiago H de Paula Figueiredo
On Tue, 26 Feb 2013 00:45:51 -0300, mvchris wrote: Oh maan. what an idiot. That's a lesson in reading the stack trace carefully. Bad programmer. It's normal to overlook stuff sometimes . . . :) On looking back at the last message, line 31 just had a loop qmEvents.get(i).getClass

Re: 3 days of ValueEncoder-ing, no coercion found

2013-02-25 Thread mvchris
Oh maan. 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. I

Re: 3 days of ValueEncoder-ing, no coercion found

2013-02-22 Thread Thiago H de Paula Figueiredo
Oops, now looking again at your post, now in Nabble, I've noticed something: Caused by: java.lang.ClassCastException: java.lang.String cannot be cast to org.opencsta.ctiserver.library.asterisk.managerevents.model.LibraryQueueMemberEvent at org.opencsta.eventviewer.pages.admin2.Age

Re: 3 days of ValueEncoder-ing, no coercion found

2013-02-22 Thread Thiago H de Paula Figueiredo
On Fri, 22 Feb 2013 17:17:10 -0300, mvchris wrote: Hi Thiago, Hi! However, since tidying up and gaining a better understanding, the no coercion exception only appears on a grid - I made all my pages as similar as possible for this problem since the start of the week to nut it out - so m

Re: 3 days of ValueEncoder-ing, no coercion found

2013-02-22 Thread mvchris
Hi Thiago, Thanks for the response, I wasn't aware the Loop/Grid thing was a big issue - with either template it had been the same, passing the ValueEncoder. However, since tidying up and gaining a better understanding, the no coercion exception only appears on a grid - I made all my pages as sim

Re: 3 days of ValueEncoder-ing, no coercion found

2013-02-22 Thread Thiago H de Paula Figueiredo
On Fri, 22 Feb 2013 06:09:42 -0300, mvchris wrote: Happy Friday Tapestry Users, Hi! I've been stuck on this all week and really can't move because it's the last part of my app :( I don't understand this thread. Really. We've noticed the problem is in a Loop. Now you post a template wit

Re: 3 days of ValueEncoder-ing, no coercion found

2013-02-22 Thread mvchris
Happy Friday Tapestry Users, I've been stuck on this all week and really can't move because it's the last part of my app :( Then I'm done!! But tapestry is not making it easy to finish. My ValueEncoder is not getting recognised. Here's a good summary of it. 1. I use similar (if not the exact

Re: 3 days of ValueEncoder-ing, no coercion found

2013-02-20 Thread mvchris
I took it out when doing my side-project testing. The findAll() works without a ValueEncoder, yet the other query does not. Here is a ValueEncoder I have used but no luck. Why does findAll() work without a value encoder and the other one doesn't? This part seems irregular. /* * To change this

Re: 3 days of ValueEncoder-ing, no coercion found

2013-02-20 Thread Thiago H de Paula Figueiredo
On Wed, 20 Feb 2013 18:25:28 -0300, mvchris wrote: Hi Thiago et al, Sure can, what follows is the template, page class, session bean, implementation and entity with named queries. You didn't explicitly provided a ValueEncoder to your source. Could you please try that? -- Thiago H. de Pau

Re: 3 days of ValueEncoder-ing, no coercion found

2013-02-20 Thread mvchris
nabble ate my template, hopefully the raw tag works. -- View this message in context: http://tapestry.1045711.n5.nabble.com/3-days-of-ValueEncoder-ing-no-coercion-found-tp5720109p5720131.html Sent from the Tapestry - User mailing list archive at Nabble.com.

Re: 3 days of ValueEncoder-ing, no coercion found

2013-02-20 Thread mvchris
Hi Thiago et al, Sure can, what follows is the template, page class, session bean, implementation and entity with named queries. I discovered this behaviour when I ripped this stuff out into a side project and made a mock list of objects to display...and it worked. Note that there are no complex

Re: 3 days of ValueEncoder-ing, no coercion found

2013-02-20 Thread Thiago H de Paula Figueiredo
On Wed, 20 Feb 2013 09:54:15 -0300, mvchris wrote: Whether I use a grid or a loop, my EJB findAll() method which returns all records - it displays the records without a problem. If I use my getDistinct() method, I get the no coercion error. This may be related to the JPA implementation return

Re: 3 days of ValueEncoder-ing, no coercion found

2013-02-20 Thread mvchris
Noted the use of DefaultProvider where grid's is optional. And yes, I remember reading a million times not to do what I posted - thanks for highlighting that! -- View this message in context: http://tapestry.1045711.n5.nabble.com/3-days-of-ValueEncoder-ing-no-coercion-found-tp5720109p5720119.ht

Re: 3 days of ValueEncoder-ing, no coercion found

2013-02-20 Thread mvchris
OK - I have some peculiar repeatable behaviour... (no use of value encoder for testing and my findAll() works but smaller subset of results, still List object used for source) Whether I use a grid or a loop, my EJB findAll() method which returns all records - it displays the records without a pro

Re: 3 days of ValueEncoder-ing, no coercion found

2013-02-20 Thread Thiago H de Paula Figueiredo
On Wed, 20 Feb 2013 01:49:36 -0300, Chris Mylonas wrote: Hi Tapestry List, long time no hear... Hi! Welcome back! There are no lmevents to display; you can add some manually when the link is made. Have you checked in the Tapestry err

Re: 3 days of ValueEncoder-ing, no coercion found

2013-02-19 Thread mvchris
Thanks for the pointers Taha - interesting that those ValueEncoders have slightly different behaviours depending Let me get some traces with a smaller sample project to try and help my cause. It's my first tapestry project in nearly a year! -- View this message in context: http://tapestry.104

Re: 3 days of ValueEncoder-ing, no coercion found

2013-02-19 Thread Chris Mylonas
Excuse me, the contribute method in the previous email was not the one used for coercion errors. It should have looked like this public static void contributeValueEncoderSource( MappedConfiguration, ValueEncoderFactory> configuration) { configuration.addInstance(LibraryEv

Re: 3 days of ValueEncoder-ing, no coercion found

2013-02-19 Thread Taha Siddiqi
Hi Chris You have not shared the trace so I can't help you much but there are certain things I thought might help in general. Contributing a ValueEncoder to a ValueEncoderSource only helps in components which use the ComponentDefaultProvider#defaultValueEncoder e.g. Select, Palette etc. For a