Paulo Gaspar wrote:
>
> I think you are right about pushing it to the application level.
> This is the kind of thing that can have too many use cases.
That's my worry : that it will rapidly blossom into a hairball, whereas
lots of the things that are important, like connections, permissions,
etc are all something that have to be dealt with at the app layer.
> Maybe the best I can do is to provide a JDBC sample.
It can be a working class, not just a sample. I have always thought
that the resource management is an app issue, with all vel really
needing was an interface to take a String / InputStream / etc, but the
file stuff is *so* pervasive, including it makes sense. Of course, we
then got into issues dealing with things like the application root when
in a servlet container, and the question there was do we deal with this
in Velocity by providing a 'ServletTemplateLoader' or something that
knows about life in a servlet runner, or leave it to the app, providing
support maybe in VelocityServlet? I originally thought we should
provide a loader, but was eventually convinced that wasn't really the
right way to go. Turbine handles it just fine, for example, w/o extra
support (that will have to be maintained) in Velocity.
>
> Paulo
>
> > -----Original Message-----
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Geir
> > Magnusson Jr.
> >
> > Paulo Gaspar wrote:
> > >
> > > > Jason too care of that a while ago. A JDBC loader? :)
> > > >
> > > > geir
> > >
> > > Yeahp. I work a lot with JDBC and it would be easy for me.
> > > Feature sugestions?
> >
> > First, yeah, I think this would be useful for people. (Of course,
> > what's wrong with your filesystem ?)
> >
> > However (there had to be a however, right... :) I live in the "what can
> > be pushed to application layer should be pushed into application layer"
> > camp a lot of the time, and wonder if this would be a great tool for
> > applications.
> >
> > Something that would return a Template so you could use it in servlets
> > or in apps. That would then punt what could be ugly permissions /
> > config / setup / connection pooling / etc issues to the application
> > layer, where that stuff is usually handled already anyway.
> >
> > Thoughts?
> >
> > geir
> >
> >
> > --
> > Geir Magnusson Jr. [EMAIL PROTECTED]
> > Velocity : it's not just a good idea. It should be the law.
> > http://jakarta.apache.org/velocity
> >
--
Geir Magnusson Jr. [EMAIL PROTECTED]
Velocity : it's not just a good idea. It should be the law.
http://jakarta.apache.org/velocity
