You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Angelo Chen <an...@yahoo.com.hk> on 2009/05/28 12:18:10 UTC
t5: id or t:id
a quick question, why id="" does not work, has to be t:id? then why context
works?
Delete
thanks
--
View this message in context: http://www.nabble.com/t5%3A-id-or-t%3Aid-tp23758987p23758987.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: Loop.restoreStateFromStoredClientValue.... in 5.1.0.5
Posted by Tom Zurkan <tz...@citizensportsinc.com>.
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
Re: Loop.restoreStateFromStoredClientValue.... in 5.1.0.5
Posted by Robert Zeigler <ro...@scazdl.org>.
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
Re: Loop.restoreStateFromStoredClientValue.... in 5.1.0.5
Posted by Tom Zurkan <tz...@citizensportsinc.com>.
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
Re: 5.0.1.8 to 5.1.0.5... still getting Resource service not available....
Posted by Tom Zurkan <tz...@citizensportsinc.com>.
nevermind... my bad... we are decorating the asset source and i didn't
implement the new getResource method... works now... that had me stumped
for a while... :)
thanks for the great learning experience!
tom
Tom Zurkan wrote:
> deleted my repository and rebuilt it to make sure that only 5.1.0.5
> was available. still got the same problem. i have the following in
> my classpath for tapestry:
>
> develop/m2repo/repository/org/apache/tapestry/tapestry-core/5.1.0.5/tapestry-core-5.1.0.5.jar
>
> :/develop/m2repo/repository/org/apache/tapestry/tapestry-ioc/5.1.0.5/tapestry-ioc-5.1.0.5.jar
>
> :/develop/m2repo/repository/org/apache/tapestry/tapestry-spring/5.1.0.5/tapestry-spring-5.1.0.5.jar
>
> :/develop/m2repo/repository/org/apache/tapestry/tapestry-upload/5.1.0.5/tapestry-upload-5.1.0.5.jar
>
> :/develop/m2repo/repository/org/apache/tapestry/tapestry5-annotations/5.1.0.5/tapestry5-annotations-5.1.0.5.jar
>
>
> do i need to include tapestry-test? weird. i created a dummy builder
> for resource that returns a context resource which works but can't be
> right.
>
> here is the error from the logs:
>
> 2009-05-29 13:52:45,247 [btpool0-1] ERROR
> org.apache.tapestry5.ioc.Registry - No service implements the
> interface org.apache.tapestry5.ioc.Resource.
> 2009-05-29 13:52:45,247 [btpool0-1] ERROR
> org.apache.tapestry5.ioc.Registry - Operations trace:
> 2009-05-29 13:52:45,247 [btpool0-1] ERROR
> org.apache.tapestry5.ioc.Registry - [ 1] Realizing service PagePool
> 2009-05-29 13:52:45,247 [btpool0-1] ERROR
> org.apache.tapestry5.ioc.Registry - [ 2] Invoking
> org.apache.tapestry5.internal.services.InternalModule.buildPagePool(PagePoolImpl,
> InvalidationEventHub, InvalidationEventHub) (at InternalModule.java:188)
> 2009-05-29 13:52:45,247 [btpool0-1] ERROR
> org.apache.tapestry5.ioc.Registry - [ 3] Realizing service
> ComponentMessagesInvalidationEventHub
> 2009-05-29 13:52:45,247 [btpool0-1] ERROR
> org.apache.tapestry5.ioc.Registry - [ 4] Invoking
> org.apache.tapestry5.services.TapestryModule.buildComponentMessagesInvalidationEventHub(ComponentMessagesSource)
> (at TapestryModule.java:2246)
> 2009-05-29 13:52:45,247 [btpool0-1] ERROR
> org.apache.tapestry5.ioc.Registry - [ 5] Realizing service
> ComponentMessagesSource
> 2009-05-29 13:52:45,247 [btpool0-1] ERROR
> org.apache.tapestry5.ioc.Registry - [ 6] Invoking
> org.apache.tapestry5.internal.services.InternalModule.buildComponentMessagesSource(ComponentMessagesSourceImpl)
> (at InternalModule.java:129)
> 2009-05-29 13:52:45,247 [btpool0-1] ERROR
> org.apache.tapestry5.ioc.Registry - [ 7] Determining injection value
> for parameter #1
> (org.apache.tapestry5.internal.services.ComponentMessagesSourceImpl)
> 2009-05-29 13:52:45,248 [btpool0-1] ERROR
> org.apache.tapestry5.ioc.Registry - [ 8] Resolving object of type
> org.apache.tapestry5.internal.services.ComponentMessagesSourceImpl
> using MasterObjectProvider
> 2009-05-29 13:52:45,248 [btpool0-1] ERROR
> org.apache.tapestry5.ioc.Registry - [ 9] Autobuilding instance of
> class org.apache.tapestry5.internal.services.ComponentMessagesSourceImpl
> 2009-05-29 13:52:45,248 [btpool0-1] ERROR
> org.apache.tapestry5.ioc.Registry - [10] Determining injection value
> for parameter #1 (org.apache.tapestry5.ioc.Resource)
> 2009-05-29 13:52:45,248 [btpool0-1] ERROR
> org.apache.tapestry5.ioc.Registry - [11] Resolving object of type
> org.apache.tapestry5.ioc.Resource using MasterObjectProvider
> 2009-05-29 13:52:45,249 [btpool0-1] ERROR
> org.apache.tapestry5.internal.services.InternalModule.ComponentMessagesSource
> - Construction of service ComponentMessagesSource failed: Error
> invoking service builder method
> org.apache.tapestry5.internal.services.InternalModule.buildComponentMessagesSource(ComponentMessagesSourceImpl)
> (at InternalModule.java:129) (for service 'ComponentMessagesSource'):
> Error invoking constructor
> org.apache.tapestry5.internal.services.ComponentMessagesSourceImpl(Resource,
> ClasspathURLConverter) (at ComponentMessagesSourceImpl.java:73) (for
> service 'ComponentMessagesSource'): No service implements the
> interface org.apache.tapestry5.ioc.Resource.
> java.lang.RuntimeException: Error invoking service builder method
> org.apache.tapestry5.internal.services.InternalModule.buildComponentMessagesSource(ComponentMessagesSourceImpl)
> (at InternalModule.java:129) (for service 'ComponentMessagesSource'):
> Error invoking constructor
> org.apache.tapestry5.internal.services.ComponentMessagesSourceImpl(Resource,
> ClasspathURLConverter) (at ComponentMessagesSourceImpl.java:73) (for
> service 'ComponentMessagesSource'): No service implements the
> interface org.apache.tapestry5.ioc.Resource.
> at
> org.apache.tapestry5.ioc.internal.ServiceBuilderMethodInvoker.createObject(ServiceBuilderMethodInvoker.java:76)
>
>
> ---------------------------------------------------------------------
> 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
5.0.1.8 to 5.1.0.5... still getting Resource service not available....
Posted by Tom Zurkan <tz...@citizensportsinc.com>.
deleted my repository and rebuilt it to make sure that only 5.1.0.5 was
available. still got the same problem. i have the following in my
classpath for tapestry:
develop/m2repo/repository/org/apache/tapestry/tapestry-core/5.1.0.5/tapestry-core-5.1.0.5.jar
:/develop/m2repo/repository/org/apache/tapestry/tapestry-ioc/5.1.0.5/tapestry-ioc-5.1.0.5.jar
:/develop/m2repo/repository/org/apache/tapestry/tapestry-spring/5.1.0.5/tapestry-spring-5.1.0.5.jar
:/develop/m2repo/repository/org/apache/tapestry/tapestry-upload/5.1.0.5/tapestry-upload-5.1.0.5.jar
:/develop/m2repo/repository/org/apache/tapestry/tapestry5-annotations/5.1.0.5/tapestry5-annotations-5.1.0.5.jar
do i need to include tapestry-test? weird. i created a dummy builder
for resource that returns a context resource which works but can't be right.
here is the error from the logs:
2009-05-29 13:52:45,247 [btpool0-1] ERROR
org.apache.tapestry5.ioc.Registry - No service implements the interface
org.apache.tapestry5.ioc.Resource.
2009-05-29 13:52:45,247 [btpool0-1] ERROR
org.apache.tapestry5.ioc.Registry - Operations trace:
2009-05-29 13:52:45,247 [btpool0-1] ERROR
org.apache.tapestry5.ioc.Registry - [ 1] Realizing service PagePool
2009-05-29 13:52:45,247 [btpool0-1] ERROR
org.apache.tapestry5.ioc.Registry - [ 2] Invoking
org.apache.tapestry5.internal.services.InternalModule.buildPagePool(PagePoolImpl,
InvalidationEventHub, InvalidationEventHub) (at InternalModule.java:188)
2009-05-29 13:52:45,247 [btpool0-1] ERROR
org.apache.tapestry5.ioc.Registry - [ 3] Realizing service
ComponentMessagesInvalidationEventHub
2009-05-29 13:52:45,247 [btpool0-1] ERROR
org.apache.tapestry5.ioc.Registry - [ 4] Invoking
org.apache.tapestry5.services.TapestryModule.buildComponentMessagesInvalidationEventHub(ComponentMessagesSource)
(at TapestryModule.java:2246)
2009-05-29 13:52:45,247 [btpool0-1] ERROR
org.apache.tapestry5.ioc.Registry - [ 5] Realizing service
ComponentMessagesSource
2009-05-29 13:52:45,247 [btpool0-1] ERROR
org.apache.tapestry5.ioc.Registry - [ 6] Invoking
org.apache.tapestry5.internal.services.InternalModule.buildComponentMessagesSource(ComponentMessagesSourceImpl)
(at InternalModule.java:129)
2009-05-29 13:52:45,247 [btpool0-1] ERROR
org.apache.tapestry5.ioc.Registry - [ 7] Determining injection value for
parameter #1
(org.apache.tapestry5.internal.services.ComponentMessagesSourceImpl)
2009-05-29 13:52:45,248 [btpool0-1] ERROR
org.apache.tapestry5.ioc.Registry - [ 8] Resolving object of type
org.apache.tapestry5.internal.services.ComponentMessagesSourceImpl using
MasterObjectProvider
2009-05-29 13:52:45,248 [btpool0-1] ERROR
org.apache.tapestry5.ioc.Registry - [ 9] Autobuilding instance of class
org.apache.tapestry5.internal.services.ComponentMessagesSourceImpl
2009-05-29 13:52:45,248 [btpool0-1] ERROR
org.apache.tapestry5.ioc.Registry - [10] Determining injection value for
parameter #1 (org.apache.tapestry5.ioc.Resource)
2009-05-29 13:52:45,248 [btpool0-1] ERROR
org.apache.tapestry5.ioc.Registry - [11] Resolving object of type
org.apache.tapestry5.ioc.Resource using MasterObjectProvider
2009-05-29 13:52:45,249 [btpool0-1] ERROR
org.apache.tapestry5.internal.services.InternalModule.ComponentMessagesSource
- Construction of service ComponentMessagesSource failed: Error invoking
service builder method
org.apache.tapestry5.internal.services.InternalModule.buildComponentMessagesSource(ComponentMessagesSourceImpl)
(at InternalModule.java:129) (for service 'ComponentMessagesSource'):
Error invoking constructor
org.apache.tapestry5.internal.services.ComponentMessagesSourceImpl(Resource,
ClasspathURLConverter) (at ComponentMessagesSourceImpl.java:73) (for
service 'ComponentMessagesSource'): No service implements the interface
org.apache.tapestry5.ioc.Resource.
java.lang.RuntimeException: Error invoking service builder method
org.apache.tapestry5.internal.services.InternalModule.buildComponentMessagesSource(ComponentMessagesSourceImpl)
(at InternalModule.java:129) (for service 'ComponentMessagesSource'):
Error invoking constructor
org.apache.tapestry5.internal.services.ComponentMessagesSourceImpl(Resource,
ClasspathURLConverter) (at ComponentMessagesSourceImpl.java:73) (for
service 'ComponentMessagesSource'): No service implements the interface
org.apache.tapestry5.ioc.Resource.
at
org.apache.tapestry5.ioc.internal.ServiceBuilderMethodInvoker.createObject(ServiceBuilderMethodInvoker.java:76)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: Loop.restoreStateFromStoredClientValue.... in 5.1.0.5
Posted by Robert Zeigler <ro...@scazdl.org>.
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
Re: Loop.restoreStateFromStoredClientValue.... in 5.1.0.5
Posted by Tom Zurkan <tz...@citizensportsinc.com>.
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
Re: Loop.restoreStateFromStoredClientValue.... in 5.1.0.5
Posted by Siddhartha Argollo <sl...@tre-ba.gov.br>.
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
>
>
--
Siddhartha Argollo
Técnico Judiciário
TRE-BA / SEDESI - Seção de Desenvolvimento de Sistemas
slargollo@tre-ba.gov.br
3373-7137
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Loop.restoreStateFromStoredClientValue.... in 5.1.0.5
Posted by Tom Zurkan <tz...@citizensportsinc.com>.
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
Re: t5: id or t:id
Posted by Ulrich Stärk <ul...@spielviel.de>.
Angelo Chen schrieb:
> a quick question, why id="" does not work, has to be t:id? then why context
> works?
I've got the feeling that I'm answering this again and again. Why can't you search the archives?
id is an attribute of the (X)HTML namespace while t:id is from the Tapestry namespace. Since they
would collide they need to be in different namespaces (apart from that they also have different
semantics).
>
> Delete
Delete what?
>
> thanks
You're welcome.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org