[JIRA-OS] Commented: (WW-251) Add velocity helpers (including macros) back to ww2

The following comment has been added to this issue:

     Author: Patrick Lightbody
    Created: Sun, 14 Sep 2003 6:58 PM
       Body:
"action" is in CVS, others should be here soon
---------------------------------------------------------------------
View the issue:

  http://jira.opensymphony.com/secure/ViewIssue.jspa?key=WW-251


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: WW-251
    Summary: Add velocity helpers (including macros) back to ww2
       Type: Improvement

     Status: Assigned
   Priority: Minor

    Project: WebWork
 Components: 
             Misc
   Fix Fors:
             2.0-beta2
   Versions:
             2.1
             2.0-beta2
             2.0-beta1

   Assignee: Patrick Lightbody
   Reporter: Drew McAuliffe

    Created: Tue, 12 Aug 2003 8:01 PM
    Updated: Wed, 13 Aug 2003 11:16 PM

Description:
The velocity helper class from 1.3 (webwork.view.velocity.WebWorkUtil) has been removed from 2.0. It had a number of useful features that help when working with velocity views. For example, "action", "execute", "bean", "include", and "evaluate". 

Several of these methods can be duplicated using velocity macros that call on the value stack. But the old macros haven't been replaced either. The "evaluate" method was especially helpful, since it could evaluate a runtime expression against the velocity context. While you could evaluate something against the value stack, I'm not sure that it's the same thing and there might be cases where you'd want to do both.

I've attached the following:
1) Sample ww2 macros that reproduce the functionality of the old macros (for the most part). Some of these use the updated ww velocity utility
2) The ported velocity utility. All of the methods in this can be safely ignored except "evaluate", since everything else I do using the macros. Though "bean" duplicates the function of the old "bean" function and might be worth copying over as well. It seems to cache class objects per request, which might lead to some performance advantages (though you're always creating new instances off of them, so I don't know how much of an advantage).
3) The updated velocity manager, which adds the webwork utility to the velocity context. This copys what I thought was happening in ww1, but may not be optimal since I'm still new to ww2. I've been having some weird performance issues and they might be related to this.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.opensymphony.com/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf