All,
Maybe I'm missing something here, maybe I'm not, but I'm attempting to
preserve state JUST BETWEEN REQUESTS and I'm really struggling (I know
in T5 there's <really> two requests, but for simplicity's sake let's
just call the round trip from the browser a "request").
My options are:
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 someone leaves the page?
2) @Persist("flash")
- This is really only useful for messages and other objects that are
reliably referenced once. This is NOT "request-scoped persistence".
3) @Persist("client")
- While I thought initially thought that this would solve all my woes,
instead every link in my application now carries around an huge encoded
state variable in the URL. I'm completely missing the benefit of this
versus just using session persistence (enlightenment appreciated).
4) Activation context magic
- While this does make for clean and nifty URLs, the hassle of
constructing the identifiers for complex objects and creating the
contexts for them has not proven "worth it" to me (hint: composite
primary keys are almost unusable). Also, if your page uses more than
one dynamically-sized collection of objects, then you're out of luck.
PLEASE PLEASE don't interpret this as Tapestry-bashing. Tapestry has
been a delight to work with compared to previous frameworks I've used.
I'm just really struggling with how to do something that, IMHO, a web
framework should make very simple (request-scoped persistence).
Anyone solve this riddle yet?
Joel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
