Shawn Bayern wrote:
On Thu, 19 Dec 2002, Wendy Smoak wrote:Glass houses, stones, and all, but I think it's a yicky solution, far too dependent on nothing ever changing :) If I were doing it I'd explore other options (storing user prefs in a db indexed by a cookie value, for instance) and work off of that. Having position-dependent values seems an invitation to fragility.
<x:if select="{$showAddress}" >You can indeed read the cookie with expressions like ${cookie.key} in most
<table><tr><td>stuff</td></tr></table>
</x:if>
Or can I get at the cookie with JSTL? (And pick out a specific position of
it??) The setting of the cookie is done in a Struts Action, so I've got
Struts (and Struts-EL) tags available if one of those would be easier to
use.
cases, but you won't be able to get at a character position easily in the
cookie -- at least not under JSTL 1.0. However, if you delimit the
cookie's value with commas (e.g., "Y,N,N,Y,..."), you could in principle
loop over the cookie's components with <c:forEach> and set different
variables depending on what each individual value equals. The rough form
of this solution looks like
<c:forEach items="${cookie.foo}" var="e" varStatus="c">
<c:if test="${e == 'Y'}">
<c:set target="${myMap}" property="boolean${c.count}" value="${true}" />
</c:if>
</c:forEach>
If you're dead-set on positional keys, maybe just using an integer and doing bit compares (I don't know how/if that works under JSTL, but it's a trivial custom tag) or something... Or just use a custom tag for the YNYNYYNN method, I suppose. Obviously the db (or similar) solution is more robust and mutable.
Just my $0.02, sorry :)
Dave
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
