Re: Stale Link Exceptions

> Hi Tobias
>
> I assume you meant Trails 1.1.1 when you said Tapestry 1.1....
> I couldn't reproduce this behavior using Trails 1.1.1, can you try to
> reproduce it using the "simple" example from Trails 1.1.1 and give me
> more specifics.
> I once had issues with form submissions under opera
> (http://jira.codehaus.org/browse/TRAILS-64) and I fix them adding
> Pragma, Cache-Control and Expires meta headers. Take a look at the
> diff
> http://fisheye.codehaus.org/viewrep/trails/trunk/trails/archetypes/trails-archetype/src/main/resources/archetype-resources/src/main/webapp/WEB-INF/Border.html?r1=818&r2=912
> It might help.
>
> Conditional and Foreach are deprecated since Tapestry 4.1 (and Trails
> shouldn't be using either) . Currently If, Else, and For components
> are a part of the Tapestry (4.1.x) core distribution.
>
>
> --
> Alejandro Scandroli - http://weblog.amneris.es/
> Amneris: We build process-driven web applications.
> http://www.amneris.es
>
>
> On Fri, Feb 29, 2008 at 11:07 AM,  <superoverdrive@...> wrote:
> > By the way, on the t-deli page I saw the following:
> >
> >  Alternative base components
> >
> >  Version: 1.1
> >
> >  The If, Else, and For components provided by the Base library are
> similar to the Conditional and Foreach components that are a part of the
> Tapestry core distribution, but provide the following additional features:
> >
> >     * If the components are located in a Form, they automatically
> generate Hidden fields and ensure that the form will rewind as it was rendered
> and no stale link exceptions will occur.
> >       The components can be viewed as a combination of the general
> Tapestry components (e.g. Conditional, Foreach) and their form-specific versions
> (e.g. FormConditional, ListEdit).
> >
> >
> >  Maybe this is describing a similar issue?
> >  -------- Original-Nachricht --------
> >  > Datum: Fri, 29 Feb 2008 11:01:21 +0100
> >  > Von: superoverdrive@...
> >  > An: users@..., users@...
> >
> >
> > > Betreff: Re: [trails-users] Stale Link Exceptions
> >
> >  > Thanks!
> >  >
> >  > I am using Tapestry 1.1...but probably upgrading soon because of the
> >  > eager/lazy fetch problem.
> >  >
> >  > You can really reproduce this error easily if you:
> >  >
> >  > - open the Firebug Tool in Firefox
> >  > - go to a Tapestry page with form fields and submit the page
> >  > (here in 3 out of 5 form submissions, there is this error).
> >  >
> >  > Without Firebug open, this erro occurs 1 in 10 cases roughly.
> >  >
> >  >
> >  > -------- Original-Nachricht --------
> >  > > Datum: Fri, 29 Feb 2008 10:16:40 +0100
> >  > > Von: "Alejandro Scandroli" <alejandroscandroli@...>
> >  > > An: users@...
> >  > > Betreff: Re: [trails-users] Stale Link Exceptions
> >  >
> >  > > Hi Tobias
> >  > >
> >  > > I think that what you are describing is not a Tapestry bug, it's a
> >  > > Tapestry feature that prevents the misuse of some types of Tapestry
> >  > > links. For instance DirectLinks inside a For loop shouldn't be
> >  > > bookmarked, because the urls doesn't contain all the information
> >  > > Tapestry needs to rewind the page correctly. So if Tapestry founds
> >  > > that there is no enough information to proceed it throws an SLE.
> >  > > I have never had SLEs with Forms but I think the same principle
> could
> >  > > apply. I will do some tests. Which Trails version are you using?
> >  > >
> >  > > Alejandro
> >  > >
> >  > > --
> >  > > Alejandro Scandroli - http://weblog.amneris.es/
> >  > > Amneris: We build process-driven web applications.
> >  > > http://www.amneris.es
> >  > >
> >  > >
> >  > >
> >  > > On Thu, Feb 28, 2008 at 4:11 PM,  <superoverdrive@...> wrote:
> >  > > > Hi there!
> >  > > >
> >  > > >  I have noticed random Stale Link Exceptions that keep on
> occuring in
> >  > a
> >  > > Trails application.
> >  > > >
> >  > > >  I have also found a way that will reproduce this quite easily:
> If you
> >  > > use Firefox & Firebug and Firebug is opened, this will almost
> always
> >  > result
> >  > > in Stale Links Exceptions when forms are submitted - maybe Firebug
> >  > > re-arranges the order in which the parameters are passed...
> >  > > >
> >  > > >  Is there a work-around to fix this in a Trails application? (I
> assume
> >  > > this is a Tapestry bug?)
> >  > > >
> >  > > >  Thanks!
> >  > > >
> >  > > >  Tobias
> >  > > >
> >  > > >
> ---------------------------------------------------------------------
> >  > > >  To unsubscribe from this list, please visit:
> >  > > >
> >  > > >     http://xircles.codehaus.org/manage_email
> >  > > >
> >  > > >
> >  > > >
> >  > >
> >  > >
> ---------------------------------------------------------------------
> >  > > To unsubscribe from this list, please visit:
> >  > >
> >  > >     http://xircles.codehaus.org/manage_email
> >  > >
> >  >
> >  > ---------------------------------------------------------------------
> >  > To unsubscribe from this list, please visit:
> >  >
> >  >     http://xircles.codehaus.org/manage_email
> >  >
> >
> >  ---------------------------------------------------------------------
> >  To unsubscribe from this list, please visit:
> >
> >     http://xircles.codehaus.org/manage_email
> >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>     http://xircles.codehaus.org/manage_email
>