Ok, i've actually tested the component and have confirmed that it doesn't
work for me either.
After some fiddling there seems to be two problems with the component:

- The XTitle implementation is adding this javascript code:

requestObject.onreadystatechange = function() {if
(requestObject.readyState== 4) {
  if (requestObject.status == 200) {
     var data = extractData(requestObject);
     TimeoutSessionRenewed(data);
}
}
}

What this does is renew the warning counter every time u even move ur mouse
over the web page. To try this, refresh ur page where the timeout component
is and go for a coffee or something. Just be sure to not touch ur mouse. See
if anything happens this way.


- Second problem. The Timeout component add TimeoutConfirm() to the window
timeout event and not tapestry.TimeoutConfirm(). This throws a javascript
error when the timeout occurs and the window tries to call the non
existent TimeoutConfirm()
function.


I only tried in Firefox so IE might have a different behaviour.


On 7/17/07, Hugo Palma <[EMAIL PROTECTED]> wrote:

 Are you sure ur application is creating a session ?
Add this to ur page class:

@InjectObject("infrastructure:request")
    public abstract WebRequest getRequest();

    public boolean isInSession() {
        return getRequest().getSession(false) != null;
    }

and print out the value of the inSession property. Does it confirm that u
r in a session ?

Henry Chen wrote:

For some reason, when I post from Nable the code parts were lost. I'm
reposting from outlook this time.

Thank you for helping.

Sorry I didn't realize that the code is missing from my original post.
Here it is:

<span jwcid="@contrib:Timeout" warningTime="100" disableAutoProlong="true"/>

There is no js error. I read the generated js code and it looks like
warningTime should be in millisecond. So I tried the following which didn't
work either.

<span jwcid="@contrib:Timeout" warningTime="60000"
disableAutoProlong="true"/>


-----Original Message-----
From: Henry Chen [mailto:[EMAIL PROTECTED] <[EMAIL PROTECTED]>]
Sent: Tuesday, July 17, 2007 10:27 AM
To: users@tapestry.apache.org
Subject: Re: contrib:Timeout


Thank you for helping.

Sorry I didn't realize that the code is missing from my original post.
Here it is:



There is no js error. I read the generated js code and it looks like
warningTime should be in millisecond. So I tried the following which didn't
work either.






HugoPalma wrote:


 Did the session actually expire after the 10 minutes wait ?
What parameters did u provide to the TimeoutComponent and what are their
values ?
Did u check for javascript errors on the page ?

Henry Chen wrote:

 Nobody had the similar experience? Can anybody help? Thank you very much
in
advance.


Henry Chen wrote:

       I'm using the latest Tap4.1.2.

Did anybody successfully use contrib:Timeout?
I tried to use it in the my border component as below.



I set the session time in web.xml to 10 mins and waited but nothing
happened. I found some "timeout" related js code are added. Why didn't
it
work? Please help. Thank you.







Reply via email to