ssage-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Frederick N. Brier
Sent: Thursday, November 06, 2003 10:06 PM
To: [EMAIL PROTECTED]
Subject: Re: [OS-webwork] ValueStack being unexpectedly replaced
Ok. Answered my own question, but should the TagUtils.getStack() check
f
them
cleaned up.
> -Original Message-
> From: Frederick N. Brier [mailto:[EMAIL PROTECTED]
> Sent: Friday, November 07, 2003 1:06 AM
> To: [EMAIL PROTECTED]
> Subject: Re: [OS-webwork] ValueStack being unexpectedly replaced
>
>
> Ok. Answered my own question, but
Ok. Answered my own question, but should the TagUtils.getStack() check
for an existing value stack in an existing ActionContext before creating
one (which is, of course, empty)?
Turns out that the Webwork2 Tags extend WebWorkTagSupport and
WebWorkBodyTagSupport and utilize an accessor that cal
What are you trying to do? What do you need static methods for?
ActionContext.getContext() is a static method.
> -Original Message-
> From: Samuel Mota [mailto:[EMAIL PROTECTED]
> Sent: Monday, October 06, 2003 11:08 AM
> To: [EMAIL PROTECTED]
> Subject: [OS-webwork] ValueStack
>
>
> H
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 substitut
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:
