You know, that might be a good idea (I know I'd like it). If you could justCheck out veltag: http://jakarta.apache.org/velocity/veltag.html
create a jsp servlet that first processes the jsp, and then hooks into the
velocity template engine, you'd have the best of both worlds. I can't
think of a reason this would be a bad idea. You'd lose some of the
inherent separation that velocity imposes, but you'd gain the ability to
retrofit all your jsp apps with velocity templates in a gradual manner (or
at least use velocimacros in your jsps).
Cheers,
Scott --
Scott Eade Backstage Technologies Pty. Ltd. http://www.backstagetech.com.au
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
