It's tap4. Use the source, Luke. :)

<meta name="generator" content="Tapestry Application Framework, version
4.0"/>

You're using direct links, which also record whether or not they're
stateful. (Defaults to true if there is a current http session, false
otherwise). Set the "stateful" parameter to false on those links.

Alternatively (and this is a better approach, really), make the pages
which should be bookmarkable implement IExternalPage, then use external
links instead of direct links to do your linking.

Robert


Mark Stang wrote:
> Lindsay,
> Tap 4 or Tap 3?
> 
> Mark
> 
> 
> -----Original Message-----
> From: Lindsay Steele [mailto:[EMAIL PROTECTED]
> Sent: Wed 1/25/2006 5:04 PM
> To: Tapestry users
> Subject: Re: session=T
>  
> Hi Mark,
>               Thanks for the response.
> 
> The thing is there are no forms on the page.   As there is no 
> documentation for the current table in Tapestry 4.0,  I went and had a 
> look at the table documentation in version 3 - there is nothing there 
> about being stateful.   In any case I tried parameters session and 
> stateful in the table with values set to false and nothing seems to make 
> a difference.
> 
> The site is here http://www.ozbreeders.com
> 
> Still looking for the answer.
> 
> 
> Mark Stang wrote:
> 
>>It might be:
>>
>>stateful      boolean in      no      true    If true (the default), then the 
>>component requires an active (i.e., non-new) HttpSession when triggered. 
>>Failing that, it throws a StaleLinkException. If false, then no check is 
>>necessary. Generally, forms are stateful, but it is possible to put a 
>>stateless form onto the Home page of an application.
>>
>>This is the default for a Form:
>>
>>Form  
>>org.apache.tapestry.form.Form         
>>Non Visual Component  
>>      
>>Description 
>>A component that manages a HTML <form>. The other form-related components 
>>must be wrapped inside the Form. 
>>
>>When a form is submitted, it continues through the rewind cycle until after 
>>all of its wrapped elements have renderred. As the form component render (in 
>>the rewind cycle), they will be updating properties of the containing page 
>>and notifying thier listeners. Again: each form component is responsible not 
>>only for rendering HTML (to present the form), but for handling it's share of 
>>the form submission. Only after all that is done will the Form notify its 
>>listener.
>>See Also 
>>Button, Checkbox, FieldLabel, Hidden, ImageSubmit, ListEdit, Option, 
>>PropertySelection, Radio, RadioGroup, Submit, TextArea, TextField, Upload, 
>>ValidField    
>>Parameters 
>>
>>Name  Type    Direction       Required        Default Description     
>>listener      IActionListener         in      no              The listener, 
>>informed after the wrapped components of the form have had a chance to 
>>process their portion the request.         
>>delegate      IValidationDelegate     in      no              Object used to 
>>assist in error tracking and reporting. A single instance is shared by all 
>>ValidField and FieldLabel comopnents within a single form.    
>>stateful      boolean in      no      true    If true (the default), then the 
>>component requires an active (i.e., non-new) HttpSession when triggered. 
>>Failing that, it throws a StaleLinkException. If false, then no check is 
>>necessary. Generally, forms are stateful, but it is possible to put a 
>>stateless form onto the Home page of an application.    
>>direct        boolean in      no      true    If true (the default), then the 
>>direct service is used for the form. This decreases the amount of work 
>>required to process the form submission, and is acceptible for most forms, 
>>even those that contain Foreaches (but not those that are inside a Foreach). 
>>An abbreviated form of the rewind cycle takes place, that only references the 
>>form and the components it wraps.  
>>method        String  in      no      POST    The value to use for the method 
>>attribute of the <form> tag.    
>>
>>Body: rendered
>>Informal parameters: allowed 
>>Reserved parameters: none
>>
>>hth,
>>
>>Mark
>>
>>-----Original Message-----
>>From: Lindsay Steele [mailto:[EMAIL PROTECTED]
>>Sent: Wed 1/25/2006 3:43 PM
>>To: Tapestry users
>>Subject: session=T
>> 
>>I have a site and I am trying to make it so that users can bookmark 
>>pages.    Some of the site is protected but other sections are quite 
>>simple.   I want users to be able to bookmark them,  send them as links 
>>or search engines to return to the pages.
>>
>>The problem is that, in many links there is "session=T"   This causes 
>>the page to say the session has expired when you try to save a bookmark 
>>- the app is restarted and you never get to the page.
>>
>>When I take this out of the URL the pages load fine without a problem.
>>
>>I can't see anything on the page that is causing this, except maybe a table.
>>
>>Does anyone know what this means ? or how to get rid of it ?   Would SEF 
>>be the solution to my problems ?
>>
>>Thanks,
>>
>>           Lindsay
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: [EMAIL PROTECTED]
>>For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>>
>>  
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 
> 
> 
> ------------------------------------------------------------------------
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to