You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Tom Zurkan <tz...@citizensportsinc.com> on 2009/06/01 22:52:44 UTC

Re: Loop.restoreStateFromStoredClientValue.... in 5.1.0.5

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="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 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:
>>>>> 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-unsubscribe@tapestry.apache.org
>>>>>> For additional commands, e-mail: users-help@tapestry.apache.org
>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>>>> For additional commands, e-mail: users-help@tapestry.apache.org
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>>> For additional commands, e-mail: users-help@tapestry.apache.org
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org