Yep. I stumbled on that in the component docs and that did the trick.
I was wondering what had changed?
Siddhartha Argollo wrote:
Have you tried to set the property formState of the Loop component to
LoopFormState.NONE? That worked for me.
Tom Zurkan wrote:
it appears that the encoder/decoder now uses the type coercer. did
it use that before? i thought it used serialization or simply
toString as the default. anyway, when decoding the object, it fails
because it does find JDO->Id->Long->String to encode. but, it does
not have String->JDO decoder. now, i am just curious if that is a
change between 5.0.1.8 and 5.1.0.5?
there seems to be a default encoder being set which i'm not sure
happened before. i tried setting the loop to volatile but it fails
because source is null. this means i would either have to reload the
source list or the individual element from the db which i don't want
to do.
thanks,
tom
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
