Well - i've used that version of beanform for that exact use case during the last year... and i'm out of ideas :(
I'd have to ask for a minimum code sample that reproduces this so i can try myself... On Sun, Jun 15, 2008 at 12:12 AM, <[EMAIL PROTECTED]> wrote: > Quoting Andreas Andreou <[EMAIL PROTECTED]>: > >> Another thought, >> try cacheProperties="ognl:false" in your beanForm > > I have not been able to update to Tapestry 4.1.6-SNAPSHOT (I'm not a Maven > user). I was able to find OGNL 2.7.3 in a Maven repo to download it. I > don't > think I'm going to be able to figure out setting up Maven for my project in > a > timely manner. So any alternative way to get the jars would be nice. > > > I tried the above solution with the cacheProps attribute. No help - I still > get > the exceptions. > > I've tried excluding properties one-by-one, the only way the exceptions > aren't > thrown is when I exclude all of the properties (so it's just the buttons). > > Any other suggestions? Are they only other factors that I may have forgotten > to > include that would create something like this? > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Andreas Andreou - [EMAIL PROTECTED] - http://blog.andyhot.gr Tapestry / Tacos developer Open Source / JEE Consulting --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
