--- Drew McAuliffe <[EMAIL PROTECTED]> wrote: > My biggest problem with this is that it basically > eliminates any advantage > to using velocity as far as ease of use is > concerned. One of the main > reasons I prefer velocity over JSP is that the > syntax is more natural, > especially for things like iterations. Requiring two > extra lines makes the > whole thing ugly, unintuitive, and increases the > possibility of errors (what > if you forget to pop the item off of the stack? The > possibility of subtle, > hard to find errors over a large code base is > definitely there). Also, the > value stack should be used when it is necessary to > be used. Passing a > variable to a tag via a velocity directive doesn't > seem to me like it needs > to get the stack involved. You have a velocity > approach the moment you start > to use velocity as your templating language. The > stack is a utility object > that is available to your pages, and is obviously a > core part of the > framework, but if it doesn't need to get involved, > it shouldn't.
IMHO, block directives shall have own subcontext, and clean stack after they are done anyway.... At least I design my directives this way. regards, ===== ----[ Konstantin Pribluda ( ko5tik ) ]---------------- Zu Verstärkung meines Teams suche ich ab Sofort einen Softwareentwickler[In] für die Festanstellung. Arbeitsort: Mainz Skills: Programieren, Kentnisse in OpenSource-Bereich ----[ http://www.pribluda.de ]------------------------ __________________________________ Do you Yahoo!? Protect your identity with Yahoo! Mail AddressGuard http://antispam.yahoo.com/whatsnewfree ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork