I know this is a little off topic, but, maybe not. When talking about using jsp and velocity together I was thinking of it from a different perspective. What I thought would be nice is if you could pipe your view/templating engines.... I.E. have the application framework 1st process a file as a jsp and then feed the output to velocity and then feed the output to a cgi program or whatever. You could then use velocity to generate jsp or visa versa. Personally, I think that would be an excellent (the best?) way to migrate legacy .jsp stuff to velocity or give users the best of both worlds. My thought is that the templating engines should/could be able to be used like unix shell commands where you pipe the output of one command to the input of another.
Any thoughts? > -----Original Message----- > From: Scott Eade [mailto:[EMAIL PROTECTED] > Sent: Thursday, June 05, 2003 9:06 AM > To: Turbine Users List > Subject: Re: FLUX velocity macros available as JSPs ? > > > Michael Mainguy wrote: > > >You know, that might be a good idea (I know I'd like it). If > you could just > >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). > > > > > Check out veltag: http://jakarta.apache.org/velocity/veltag.html > > 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] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
