Fantastic idea! Worked like a charm.
Thanks,
Tom
Robert Zeigler wrote:
Sure... contribute a custom ValueEncoder for your data type? :)
Robert
On May 29, 2009, at 5/293:44 PM , Tom Zurkan wrote:
ah, knew it was something like that... thank you! gotta change all
my loops to use formState="
Sure... contribute a custom ValueEncoder for your data type? :)
Robert
On May 29, 2009, at 5/293:44 PM , Tom Zurkan wrote:
ah, knew it was something like that... thank you! gotta change all
my loops to use formState="literal:NONE" unless there is another way.
thanks again!
tom
Robert Zei
ah, knew it was something like that... thank you! gotta change all my
loops to use formState="literal:NONE" unless there is another way.
thanks again!
tom
Robert Zeigler wrote:
It used to use the PkEncoder; now it uses the ValueEncoder (which
defaults to using TypeCoercer).
Robert
On May
It used to use the PkEncoder; now it uses the ValueEncoder (which
defaults to using TypeCoercer).
Robert
On May 29, 2009, at 5/291:06 PM , Tom Zurkan wrote:
Yep. I stumbled on that in the component docs and that did the
trick. I was wondering what had changed?
Siddhartha Argollo wrote:
H
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/decode
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, w
