Tom Zurkan wrote: > > thanks! here is what i have found out so far... it is actually > happening on restore state of a loop within a form. it appears that the > encoder now uses the type coercer. did it use that before? i thought > it used serialization as the default. anyway, when decoding the object, > it fails because it does find JDO->String. but, it does not have > String->JDO. now, i am just curious if that is a change between 5.0.1.8 > and 5.1.0.5? if so, i have a lot of new coercers to write. > > thanks so much for your advise! > > tom >
Somethings have definitely changed in this area. I have 1 checkbox and 2 textfileds on my form that T5.0.18 used to coerce nicely into a custom Java object (let's call it com.xyz.mypkg.MyType) upon form submission, but now T5.1.0.5 tells me this: org.apache.tapestry5.ioc.internal.util.TapestryException: Could not find a coercion from type java.lang.String to type com.xyz.mypkg.MyType -- View this message in context: http://www.nabble.com/reporting-issues-tp23749911p23844849.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
