You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Martin Strand <ma...@entcap.se> on 2006/09/25 00:02:35 UTC
Improving client:page
I'm trying to improve the client:page scope and prevent it from adding
state to PageLinks that lead to other pages. I figured this should work if
I examine the ServiceEncoding parameters in shouldEncodeState. But almost
all encoding parameters are null... Have I completely misunderstood how
this works?
Martin
public boolean shouldEncodeState(ServiceEncoding encoding, String
pageName, PersistentPropertyData data)
{
for (String param : encoding.getParameterNames())
{
// All the params are here (service, page, sp, etc...)
// but they're all null.. :\
String value = encoding.getParameterValue(param);
}
// Match "service" and "page" parameters with the current
// request cycle to decide whether encoding is needed
}
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: Improving client:page - all ServiceEncoding params are null
Posted by Martin Strand <ma...@entcap.se>.
Oh, I see. Thanks.
Martin
On Mon, 25 Sep 2006 18:41:52 +0200, andyhot <an...@di.uoa.gr> wrote:
> http://issues.apache.org/jira/browse/TAPESTRY-770
>
> Martin Strand wrote:
>> Seems like the only ServiceEncoding parameters that aren't null are
>> "sp" for the direct service. Does anybody know how this is supposed to
>> work?
>>
>> On Mon, 25 Sep 2006 00:02:35 +0200, Martin Strand
>> <ma...@entcap.se> wrote:
>>
>>> I'm trying to improve the client:page scope and prevent it from
>>> adding state to PageLinks that lead to other pages. I figured this
>>> should work if I examine the ServiceEncoding parameters in
>>> shouldEncodeState. But almost all encoding parameters are null...
>>> Have I completely misunderstood how this works?
>>>
>>> Martin
>>>
>>> public boolean shouldEncodeState(ServiceEncoding encoding, String
>>> pageName, PersistentPropertyData data)
>>> {
>>> for (String param : encoding.getParameterNames())
>>> {
>>> // All the params are here (service, page, sp, etc...)
>>> // but they're all null.. :\
>>> String value = encoding.getParameterValue(param);
>>> }
>>>
>>>
>>> // Match "service" and "page" parameters with the current
>>> // request cycle to decide whether encoding is needed
>>> }
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: Improving client:page - all ServiceEncoding params are null
Posted by andyhot <an...@di.uoa.gr>.
http://issues.apache.org/jira/browse/TAPESTRY-770
Martin Strand wrote:
> Seems like the only ServiceEncoding parameters that aren't null are
> "sp" for the direct service. Does anybody know how this is supposed to
> work?
>
> On Mon, 25 Sep 2006 00:02:35 +0200, Martin Strand
> <ma...@entcap.se> wrote:
>
>> I'm trying to improve the client:page scope and prevent it from
>> adding state to PageLinks that lead to other pages. I figured this
>> should work if I examine the ServiceEncoding parameters in
>> shouldEncodeState. But almost all encoding parameters are null...
>> Have I completely misunderstood how this works?
>>
>> Martin
>>
>> public boolean shouldEncodeState(ServiceEncoding encoding, String
>> pageName, PersistentPropertyData data)
>> {
>> for (String param : encoding.getParameterNames())
>> {
>> // All the params are here (service, page, sp, etc...)
>> // but they're all null.. :\
>> String value = encoding.getParameterValue(param);
>> }
>>
>>
>> // Match "service" and "page" parameters with the current
>> // request cycle to decide whether encoding is needed
>> }
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
>
--
Andreas Andreou - andyhot@apache.org - http://andyhot.di.uoa.gr
Tapestry / Tacos developer
Open Source / J2EE Consulting
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: Improving client:page - all ServiceEncoding params are null
Posted by Martin Strand <ma...@entcap.se>.
Seems like the only ServiceEncoding parameters that aren't null are "sp"
for the direct service. Does anybody know how this is supposed to work?
On Mon, 25 Sep 2006 00:02:35 +0200, Martin Strand
<ma...@entcap.se> wrote:
> I'm trying to improve the client:page scope and prevent it from adding
> state to PageLinks that lead to other pages. I figured this should work
> if I examine the ServiceEncoding parameters in shouldEncodeState. But
> almost all encoding parameters are null... Have I completely
> misunderstood how this works?
>
> Martin
>
> public boolean shouldEncodeState(ServiceEncoding encoding, String
> pageName, PersistentPropertyData data)
> {
> for (String param : encoding.getParameterNames())
> {
> // All the params are here (service, page, sp, etc...)
> // but they're all null.. :\
> String value = encoding.getParameterValue(param);
> }
>
>
> // Match "service" and "page" parameters with the current
> // request cycle to decide whether encoding is needed
> }
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org