I second this, I've tried implementing some of the taglib functionality to be accessible via velocity, and it currently requires a fair amount of cut'n'pasting of code from the taglib classes. I'll open an issue in Jira for this one.
"Erik Beeson" <[EMAIL PROTECTED]> wrote in message news:Pine.GSO.4.44.0211011519340.15204-100000@;whiterabbit... > I'd suggest that the bulk of the code in the taglibs be moved to nonweb > related classes and have the taglibs wrap those classes. This would make > it easier to provide the same functionality to a different view system > that the taglibs provide without much (any?) redundancy. > > Obviously this is an XWork suggestion, not a 1.3 suggestion. > > --Erik ------------------------------------------------------- This SF.net email is sponsored by: ApacheCon, November 18-21 in Las Vegas (supported by COMDEX), the only Apache event to be fully supported by the ASF. http://www.apachecon.com _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
