I know, which is why I suggested placing the VS into the context for users,
perhaps as $valuestack or something. Its no big deal, since its easy for users
to either retrieve it themselves or to subclass WebWorkVelocityServlet...
btw, what are thoughts about including that bit on variable substitution (
action.success=foo.action?${bar}) into the 1.3 branch? I've already patched it
to work for me, using the VS. Also, I've reimplemented that bit on ${...}
"parsing" from the code in Xwork CVS. From initial tests, my implementation is
~2x faster, but only coz I deal with char arrays rather than call
string.substring. I think the code in CVS is clearer though...
KT
On Fri, 7 Mar 2003 22:30:39 -0800, Patrick Lightbody said:
>It's hard, since the VelocityContext is the only way we can provide
>integration, and Velocity has already parsed out the stuff in
>${.....}. So our WebWorkVelocityContext doesn't get "../name" when
>you do ${../name}, instead Velocity throws a parse error. :)
>
>-Pat
>
>----- Original Message -----
>From: <[EMAIL PROTECTED]> To: <opensymphony-
>[EMAIL PROTECTED]> Sent: Friday, March 07, 2003 10:05 PM
>Subject: [OS-webwork] ValueStack and Velocity
>
>
>>The WebWorkVelocityContext does a pretty good job of integrating
>>VelocityContext with ServletValueStack.
>>
>>However, as you know, you can't do ${../name}. Is there anyother
>>way to traverse the VS other than manually obtaining the VS via
>>req.getAttribute(webwork.result)? If no, perhaps the
>>WebWorkVelocityServlet should be friendly enough to add the VS into
>>the context for users?
>>
>>Just a thought. I've not using the VS much myself anyways...
>>--
>>Kelvin Tan, [EMAIL PROTECTED] on 03/08/2003
>>
>>
>>
>>
>>-------------------------------------------------------
>>This SF.net email is sponsored by: Etnus, makers of TotalView, The
>debugger
>>for complex code. Debugging C/C++ programs can leave you feeling
>>lost and disoriented. TotalView can help you find your way.
>>Available on major UNIX and Linux platforms. Try it free.
>>www.etnus.com _______________________________________________
>>Opensymphony-webwork mailing list Opensymphony-
>>[EMAIL PROTECTED]
>>https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
>
>
>
>-------------------------------------------------------
>This SF.net email is sponsored by: Etnus, makers of TotalView, The
>debugger for complex code. Debugging C/C++ programs can leave you
>feeling lost and disoriented. TotalView can help you find your way.
>Available on major UNIX and Linux platforms. Try it free.
>www.etnus.com _______________________________________________
>Opensymphony-webwork mailing list Opensymphony-
>[EMAIL PROTECTED]
>https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger
for complex code. Debugging C/C++ programs can leave you feeling lost and
disoriented. TotalView can help you find your way. Available on major UNIX
and Linux platforms. Try it free. www.etnus.com
_______________________________________________
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
