I am not sure if this is what you need, but I had problem similar to
yours and solved it this way:
You wrote:
1) @Persist("session")
- Obviously doesn't work well for just persisting values between
requests, unless someone has come up with a reliable construct for
nulling out these values whenever
Sorry ...
To: Tapestry users ; Toby Hobson <[EMAIL PROTECTED]>
Sent: Saturday, 3 May, 2008 1:05:52 AM
Subject: Re: Dynamic asset
I don't know what is.
How are you getting the url? what is it supposed to point to? A page?
an action? a static file on the server?
Josh
On Fri, May 2, 2008 at 4:14
On Sat, May 3, 2008 at 1:22 PM, Toby Hobson <[EMAIL PROTECTED]> wrote:
> The url should be a static file on the server, alternatively I could point
> it to a servlet or tapestry page which will retrieve the image from the file
> system and stream it to the user
There's already a solution for t
On Sat, May 3, 2008 at 2:40 PM, Toby Hobson <[EMAIL PROTECTED]> wrote:
>
> Thanks Massimo,
>
> Could you give me an example of how to return a link to an event handler
> from an expansion, or point me to some docs for this?
>
> Toby
>
On your teamplate you got something like...
Then on your cl
On Sat, May 3, 2008 at 3:03 PM, Toby Hobson <[EMAIL PROTECTED]> wrote:
>
> Great!
>
> Thanks!
For the records... does this belongs to wiki?! Isn't there already?
--
Massimo
http://meridio.blogspot.com
-
To unsubscribe, e-mail:
On Fri, May 2, 2008 at 6:36 PM, Joel Wiegman <[EMAIL PROTECTED]> wrote:
> Josh,
>
> Thanks for the great suggestions.
>
> I guess I'm still befuddled as to why a web framework would resist having a
> "request scope" so dilligently.
It's not resistance, it's a different mindset, one that states
The biggest argument to be made for "request scope" state that is
automatically (or framework assisted developer code) persisted in the page
vs. the "flash" technique of Tapestry is when considering multiple browsers
opened by the user with the same session. Every app that I've developed,
we've
Right. Most annoying things for us about “session” and “flash” scopes
was that they don’t work in several tabs. And “client” can’t hold too
much data.
That’s why we have implemented a new persistence strategy named “flow”
(inspired by the Spring WebFlow). The idea is that every URL has flow
