The problem is that you have to understand a lot about Tapestry to get it to
work right; other than that, it's fine (speed is not an issue).  But the
concept of repeatable renders (which, in turn, is which properties must be
persistent so as to re-render the page a second time), it difficult to
express.

----- Original Message -----
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, July 12, 2002 1:49 PM
Subject: RE: [Tapestry-developer] StaleLink Problem


> Go into a little more detail here, Howard. I know Action is slower, but
why
> is it not useful...isn't that the only service that allows for nested
> components in loops? Where am I confused?
>
> -C
>
>
> ----- Forwarded by Christian Hall/Technology/Equifax on 07/12/2002 04:51
PM
> -----
> |--------+---------------------------------------------->
> |        |          [EMAIL PROTECTED]                    |
> |        |          Sent by:                            |
> |        |          [EMAIL PROTECTED]|
> |        |          eforge.net                          |
> |        |                                              |
> |        |                                              |
> |        |          07/12/2002 04:34 PM                 |
> |        |                                              |
> |--------+---------------------------------------------->
>
>---------------------------------------------------------------------------
----------------------|
>   |
|
>   |       To:     "Adam Greene" <[EMAIL PROTECTED]>
|
>   |       cc:     [EMAIL PROTECTED] (Tapestry
Developer)                     |
>   |       Subject:     RE: [Tapestry-developer] StaleLink Problem
|
>   |
         |
>
>---------------------------------------------------------------------------
----------------------|
>
>
>
> I've found that Action is only useful in a limited
> number of cases; sometimes only during prototyping.
> Using Direct, and explicitly encoding information
> (rather than letting Action implicitly encode
> information) works better, alas.  There is no magic.
>
> Tapestry could do Action better, perhaps, but the cost
> is astronomical.  Tapestry would have to know about
> every property on the page and every property change
> would require firing of an observed change ... even if
> the property is not persistent.
>
> I abandoned this approach because the server would have
> to store dozens of individual sub-snapshots for each
> page (one for each Action rendered to HTML) ... in
> addition, it would be very hard for Tapestry to track
> any changes that occur *inside* properties (i.e., to a
> collection object that is a persistent property), or to
> the visit object.
>
> --
> [EMAIL PROTECTED]
>
> http://tapestry.sf.net
> > Thanks.  After much investigation with the programmer in question, we
> > realized that he was causing a page refresh that was trying to access a
> now
> > non-existent item.  Problem Solved.
> >
> > Man, I love open source, especially the Tapestry one, answer are quick,
> > accurate, and usable.
> >
> > Thanks a lot for all your help (especially Howard).
> >
> > Adam Greene
> > ROMulin Group Inc
> >
> > 885 Main St, Suite 16
> > Moncton, NB
> > E1C 1G5
> >
> > Ph: (506) 863-1014 x4
> > Fx: (506) 854-6886
> >
> > http://www.romulin.com/
> >
> > -----Original Message-----
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> > Sent: Friday, July 12, 2002 11:55 AM
> > To: Adam Greene
> > Subject: Re: [Tapestry-developer] StaleLink Problem
> >
> > In order to avoid getting StaleLink exceptions you must
> > ensure that your page will render identically two times
> > in a row.
> >
> > It gets rendered once to provide the page the client
> > sees in the browser.
> >
> > It gets rendered a second time in the rewind phase;
> > which is how the Action knows when to notify its
> > listener (even when there are loops and conditionals in
> > the page).
> >
> > In a CRUD (Create Update Delete) type application, your
> > page would likely have to store, as a persistent page
> > property, the primary key of the object displayed on the
> > page.
> >
> > Quite often, this is not possible (perhaps you are
> > working off of database data that can change).  In that
> > case, make use of a Direct component instead.
> >
> > Please read the Tapestry Developer's guide; it describes
> > this more fully.
> >
> >
> > --
> > [EMAIL PROTECTED]
> >
> > http://tapestry.sf.net
> > > I'm trying to use an Action component, but every time I use it, it
> > generates
> > > Stale Link pages.  What am I doing wrong?
> > >
> > > Tapestry version 2.0.2a
> > >
> > > I'm using a Visit, which should make the application stateful.  On top
> of
> > > that I thought using an Action component caused a session to be
created
> > > anyways.  When I was doing work with custom Engines and Visit object,
I
> > had
> > > to use setStateful on the engine to get the visit stateful.  Is there
> > > another issues I'm not aware of??
> > >
> > > Adam Greene
> > > ROMulin Group Inc
> > >
> > > 885 Main St, Suite 16
> > > Moncton, NB
> > > E1C 1G5
> > >
> > > Ph: (506) 863-1014 x4
> > > Fx: (506) 854-6886
> > >
> > > http://www.romulin.com/
> > >
> > >
> > >
> > >
> > > -------------------------------------------------------
> > > This sf.net email is sponsored by:ThinkGeek
> > > Gadgets, caffeine, t-shirts, fun stuff.
> > > http://thinkgeek.com/sf
> > > _______________________________________________
> > > Tapestry-developer mailing list
> > > [EMAIL PROTECTED]
> > > https://lists.sourceforge.net/lists/listinfo/tapestry-developer
> >
> >
> >
> > -------------------------------------------------------
> > This sf.net email is sponsored by:ThinkGeek
> > Gadgets, caffeine, t-shirts, fun stuff.
> > http://thinkgeek.com/sf
> > _______________________________________________
> > Tapestry-developer mailing list
> > [EMAIL PROTECTED]
> > https://lists.sourceforge.net/lists/listinfo/tapestry-developer
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Gadgets, caffeine, t-shirts, fun stuff.
> http://thinkgeek.com/sf
> _______________________________________________
> Tapestry-developer mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/tapestry-developer
>
>
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Gadgets, caffeine, t-shirts, fun stuff.
> http://thinkgeek.com/sf
> _______________________________________________
> Tapestry-developer mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/tapestry-developer



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Gadgets, caffeine, t-shirts, fun stuff.
http://thinkgeek.com/sf
_______________________________________________
Tapestry-developer mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/tapestry-developer

Reply via email to