Wes Wannemacher wrote:
No, Jon, you are right... This belongs in the action class. Just
because OGNL lets you cheat doesn't mean you should (cue Dave jumping
in any minute).
Hey!
I'm of two minds regarding this... Truncating a string is really a
view-layer issue, handled (or instigated) by a designer (which is
usually us) or a design-driven process.
That said, if it's a site-wide thing--where does it belong? Maybe a
custom tag, which is kind of a compromise: the OGNL treachery is
localized (if done in OGNL), or the scriptlet, or a utility call into
the app, etc.
If I was doing it myself I'd probably just "cheat", or create a
JSP-based custom tag that wrapped it up and hid it away.
Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
For additional commands, e-mail: user-h...@struts.apache.org
