Frank Villarreal wrote: > I tend to agree that using plain JSP+standard tags would certainly lower the > learning curve for J2 newbies. > Speaking from my personal experiences with this project, Velocity made my life much more difficult. > I'm still trying to customize layouts, menus, etc. And doing so with complex Velocity scripts sure > isn't very easy to do and/or debug ... especially when there is limited debug info (compile errors!). > Doesn't help that Velocity's site isn't documented very thoroughly. I find myself needing to do more > and more advanced stuff in Velocity that would be a snap in plain JSP ... but constrained by > Velocity's environment. This is just my 2 cents and me sharing my experience ... not a gripe. >
You definitely have a point on tracking Velocity error messages, that may really be a pain. Can you give some example of things you're finding difficult to implement with velocity ? Maybe we help you figure out the best way to implement your requirement in Velocity. -- Raphaël Luta - [EMAIL PROTECTED] Apache Portals - Enterprise Portal in Java http://portals.apache.org/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
