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

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.

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

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

Jumpstart - instantiate object comment

Hi T5 Users and Jumpstart Geoff, Whilst checking out some ValueEncoder stuff I just thought I'd ask seeing as it gets brought up a lot (Thiago/Taha) :) This example on jumpstart [1] has two ValueEncoder instantiated at the declaration of the field. As I understand this is a no-no and should be

Re: PersistenceConstants.FLASH cann't persist ListString langs

bit of a hack but can you put the list to a single string delimited by control chars or caret ^ prior to form submission then on rendering of 2nd page convert back from single string to list chris -- View this message in context:

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

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

Re: Tapestry 5, Jetty 9 + JSW

hi john, the network engineer in me asks if there is a firewall or some other impediment (like an OS level app-watching daemon that prevents programs from opening ports etc.)? is your request reaching the server if you run a network trace (like wireshark) chris -- View this message in

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

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

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

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:

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

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

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

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

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

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: