Re: tag syntax question

I totally agree with Dale, using %{..} will save you a lot of headaches. musachy On Fri, Jul 24, 2009 at 7:31 AM, Dale Newfield wrote: > Mitch Claborn wrote: >> >> Is either of the following more or less efficient than the other? >> >> >> > > I always argue that the latter should be used, just

Re: tag syntax question

3:31:36 PM Subject: Re: tag syntax question Mitch Claborn wrote: > Is either of the following more or less efficient than the other? > > > I always argue that the latter should be used, just to avoid unnecessary conf

Re: tag syntax question

Mitch Claborn wrote: Is either of the following more or less efficient than the other? I always argue that the latter should be used, just to avoid unnecessary confusion later on. -Dale - To unsubscribe, e-mail: user-uns

Re: tag syntax question

Is either of the following more or less efficient than the other? mitch Musachy Barroso wrote: > other attributes are expected to be expressions, so you can do: > > > > instead of the more verbose, but also correct: > > > > > -

Re: tag syntax question

Thanks to both. The haze on the subject is beginning to clear. mitch Musachy Barroso wrote: > yes that's a good catch Dale, from the API point of view they are > stored in a map in the ValueStack instance, but from a user point of > view you could say they are stored in the "valuestack context"

Re: tag syntax question

yes that's a good catch Dale, from the API point of view they are stored in a map in the ValueStack instance, but from a user point of view you could say they are stored in the "valuestack context". musachy On Thu, Jul 23, 2009 at 9:03 PM, Dale Newfield wrote: > Musachy Barroso wrote: >> >> Objec

Re: tag syntax question

Musachy Barroso wrote: Objects can be put in the stack by name, like the HttpServletRequest object. Theseobjects are accessed using the "#" notation, like "#request". The "set" tag can add things to the stack by name(for example). The only confusing bit about the way that was just described is

Re: tag syntax question

you need to read about the value stack. long story short, the VS stacks (duh) objects. When an expressions like: "name" is evaluated, struts will go from the top to the bottom of the stack, trying to find a "name" field or "getName" method, until one is found. Different things are placed in the s