I don't have a vote, but if I'd had one, I'd +1 anything that will make
it easier for a potential customer to separate 'product-ready' taglibs
from those that are here for historical reasons. I believe the lack of
that information is the main impediment to the wider adoption of the
useful libraries.
- eduard/o
"Ignacio J. Ortega" wrote:
>
> I think it's the moment to get rid of the SQL taglib...having JDBC
> taglib released i think the "official" SQL taglibs from jakarta should
> be yours...is awesome and deserves the name..for me send actual SQL
> taglib can go to the wastebasket without any pain.. sigh..
>
> Saludos ,
> Ignacio J. Ortega
>
> > -----Mensaje original-----
> > De: Morgan Delagrange [mailto:[EMAIL PROTECTED]]
> > Enviado el: viernes 27 de abril de 2001 17:29
> > Para: [EMAIL PROTECTED]; James Strachan
> > Asunto: Re: [VOTE] JDBC tag library name change
> >
> >
> > Good idea, but we already have a tag library in taglibs names 'SQL'.
> >
> > On Fri, 27 Apr 2001, James Strachan wrote:
> >
> > >
> > > > I would like to change the name of the JDBC tag library.
> > JDBC is a
> > > > registered trademark of Sun, and technically it cannot be
> > used within a
> > > > product name. I am:
> > > >
> > > > +1
> > > >
> > > > for changing the name of the tag library to 'DBTags', but
> > maintaining the
> > > > current packaging.
> > >
> > > Just a suggestion - how about calling them "SQL Tags" then
> > it would match
> > > your <sql:query/> style prefix?
> > >
> > > James
> > >
> > >
> > > _________________________________________________________
> > > Do You Yahoo!?
> > > Get your free @yahoo.com address at http://mail.yahoo.com
> > >
> > >
> >
> >
