|
Please see the Wiki; this is yet another thing to
be fixed in 2.4. Tapestry can, and should, be doing things
smarter.
Static bindings are primarily for strings,
nowadays. OGNL recognizes "true" and "false" literals, as well as property
path expressions and such. So, <static-binding> for string literals,
<binding> for property paths and numeric literals, and
<string-binding> for localized messages.
----- Original Message -----
Sent: Saturday, December 14, 2002 10:17
PM
Subject: Re: [Tapestry-developer] Stale
session
Dirk, thanks! This finally helped. I had been
trying to set the stateful parameter, but I finally figured out I was using a
static-binding rather than a dynamic binding. I figured since "false" was a
constant, I should use a static binding in that case, but I guess not. The
posting you directed me to caused me to look at the direct XML that Spindle
produces and I noticed the difference. As soon as I set things correctly,
things worked fine. Doh!
So this then raises another question: What are
the differences between all the various binding types that Tapestry/Spindle
supports? Should I just be using dynamic bindings everywhere? I think I got
throw off by Spindle's choices and my equating constants to "static." Had I
been editing the XML directly, I probably would have just used "binding" and
it would have worked fine. Spindle presented me with a bunch of choices and so
I picked the one that seemed the most obvious. Should I just be using dynamic
bindings every time? If not, why, when, and where would I use the other types?
Previously, I had thought that "dynamic" was just used for OGNL expressions
accessing beans. Should it be used for anything Java-like (I mean, OGNL !=
Java, so I didn't expect that "false" would be valid syntax for
that).
In any case, I read on the Wiki that somebody is
rewriting the tutorial. Some treatment of this issue would probably make
sense, particularly for people using Spindle rather than editing the XML raw.
(BTW, this is not a slam on Spindle; it's a fine tool that really helps
out.)
-- Dave
----- Original Message -----
Sent: Saturday, December 14, 2002 6:45
PM
Subject: Re: [Tapestry-developer] Stale
session
I'm using Tapestry 2.2 with Eclipse, Spindle 1.1.3, the Jetty
version packaged with Tapestry 2.2. I have written a quick little Main
class that sets up Jetty and gets things going. I have Tapestry working
enough to create a few pages, use PageLinks, a Form, etc. It's just
DirectLink that I have problems with right
now.
Can
somebody explain how, exactly, Tapestry as a framework decides the session
is stale? I even looked at the source in the DirectService class and
didn't see anything there that looked like it even checked or threw an
exception related to a stale
session.
Hmm, did you try to
make the link not stateful? See
http://sourceforge.net/mailarchive/message.php?msg_id=2214563
HTH,
-dirk
|
