You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Christofer Dutz <ma...@c-ware.de> on 2007/06/12 11:05:38 UTC
Fixed TimeToLive of JavaFlow Continuations
Hi,
I was currently analysing some of my customers bug reports and in the
course of this had to find out that there is a small "bug" in the
JavaFlowInterpreter code.
The parameter timeToLive is fixed to 600000 with no possibility of
changing this. If I should supply a patch, I willl gladly do so,
otherwise I will just have to patch it on my own ... (A quick fix would
be to set the timtToLive fixed to 0, then the
WebContinuation.createWebContinuation method would take the
defaultTimeToLive parameter from the sitemap.
Regards,
Chris
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: Fixed TimeToLive of JavaFlow Continuations
Posted by Torsten Curdt <tc...@apache.org>.
Fair enough :)
On 12.06.2007, at 12:19, Christofer Dutz wrote:
> Well the fix works great ;)
>
> simply change Line 52 of
> org.apache.cocoon.components.flow.java.JavaInterpreter from
> private int timeToLive = 600000;
> to
> private int timeToLive = 0;
>
> makes the WebContinuationManager use the defaultTimeToLive
> configured in the sitemap ... don't really know why the ttl is
> fixed anyway.
>
> Chris
>
> Torsten Curdt schrieb:
>> This has been brought up already a couple of times ...go for it
>>
>> cheers
>> --
>> Torsten
>>
>> On 12.06.2007, at 11:05, Christofer Dutz wrote:
>>
>>> Hi,
>>>
>>> I was currently analysing some of my customers bug reports and in
>>> the course of this had to find out that there is a small "bug" in
>>> the JavaFlowInterpreter code.
>>> The parameter timeToLive is fixed to 600000 with no possibility
>>> of changing this. If I should supply a patch, I willl gladly do
>>> so, otherwise I will just have to patch it on my own ... (A quick
>>> fix would be to set the timtToLive fixed to 0, then the
>>> WebContinuation.createWebContinuation method would take the
>>> defaultTimeToLive parameter from the sitemap.
>>>
>>> Regards,
>>> Chris
>>>
>>>
>>> --------------------------------------------------------------------
>>> -
>>> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
>>> For additional commands, e-mail: users-help@cocoon.apache.org
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
>> For additional commands, e-mail: users-help@cocoon.apache.org
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail: users-help@cocoon.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: Fixed TimeToLive of JavaFlow Continuations
Posted by Christofer Dutz <ma...@c-ware.de>.
Well the fix works great ;)
simply change Line 52 of
org.apache.cocoon.components.flow.java.JavaInterpreter from
private int timeToLive = 600000;
to
private int timeToLive = 0;
makes the WebContinuationManager use the defaultTimeToLive configured in
the sitemap ... don't really know why the ttl is fixed anyway.
Chris
Torsten Curdt schrieb:
> This has been brought up already a couple of times ...go for it
>
> cheers
> --
> Torsten
>
> On 12.06.2007, at 11:05, Christofer Dutz wrote:
>
>> Hi,
>>
>> I was currently analysing some of my customers bug reports and in the
>> course of this had to find out that there is a small "bug" in the
>> JavaFlowInterpreter code.
>> The parameter timeToLive is fixed to 600000 with no possibility of
>> changing this. If I should supply a patch, I willl gladly do so,
>> otherwise I will just have to patch it on my own ... (A quick fix
>> would be to set the timtToLive fixed to 0, then the
>> WebContinuation.createWebContinuation method would take the
>> defaultTimeToLive parameter from the sitemap.
>>
>> Regards,
>> Chris
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
>> For additional commands, e-mail: users-help@cocoon.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail: users-help@cocoon.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: Fixed TimeToLive of JavaFlow Continuations
Posted by Torsten Curdt <tc...@apache.org>.
This has been brought up already a couple of times ...go for it
cheers
--
Torsten
On 12.06.2007, at 11:05, Christofer Dutz wrote:
> Hi,
>
> I was currently analysing some of my customers bug reports and in
> the course of this had to find out that there is a small "bug" in
> the JavaFlowInterpreter code.
> The parameter timeToLive is fixed to 600000 with no possibility of
> changing this. If I should supply a patch, I willl gladly do so,
> otherwise I will just have to patch it on my own ... (A quick fix
> would be to set the timtToLive fixed to 0, then the
> WebContinuation.createWebContinuation method would take the
> defaultTimeToLive parameter from the sitemap.
>
> Regards,
> Chris
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail: users-help@cocoon.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org