I don't mean to be rude, Frederic, but it's not going to happen. If you want to populate controls in your applications, you can do that with the dbTags, or the JSTL when it is avialable.
If you want to extend the Struts taglibs to use that same code, you can do that too. If you want to offer such an extension to the community, I'll help promote it on my resource page. But, if we added that to the Struts taglibs, we'd also have to support it. I'm not up for that myself, and I doubt that anyone else is either. There only so many volunteer hours in the day, and supporting a Model 1 approach in a Model 2 framework is not how I want to spend mine. The Struts HTML tags are meant to be populated by the action, and then forwarded to the page, and that is the way I would suggest they be used. -- Ted Husted, Husted dot Com, Fairport NY USA. -- Java Web Development with Struts. -- Tel +1 585 737-3463. -- Web http://www.husted.com/struts/ Frederic Simard wrote: > > No, but I dont want you to duplicate it, I want you to use it. > > -----Original Message----- > From: Ted Husted [mailto:[EMAIL PROTECTED]] > Sent: Friday, February 15, 2002 2:43 PM > To: Struts Developers List > Subject: Re: feature request bug 6477 > > There is no point in Struts duplicating what is already available in > Jakarta-taglibs and what may also be in the JSTL. > > If you want to do this, use the Jakarta Taglib dbTag. > > http://jakarta.apache.org/taglibs/doc/dbtags-doc/intro.html > > Works fine with any data source, including the Struts generic data > source. > > -- Ted Husted, Husted dot Com, Fairport NY USA. > -- Java Web Development with Struts. > -- Tel +1 585 737-3463. > -- Web http://www.husted.com/struts/ > > Frederic Simard wrote: > > > > Martin for the feature request bug 6477 I don't agree with you. > > I think it could be a nice feature to be able to use SQL in or with > > Strut tag. > > > > Like they said on the > > > http://jakarta.apache.org/taglibs/doc/standard-doc/standard-ea3/DB_Funct > > ionalDescription_1_EA3.html : > > > > "Many dynamic web applications need to access relational databases for > > the dynamic aspects of their presentation layer. While it can be > argued > > that database operations should be handled in the business logic of a > > web application designed with an MVC architecture, the fact of the > > matter is that real world applications will sometimes require this > > capability within the JSP pages for various reasons (e.g. > > prototyping/testing, small scale/simple applications, lack of > developer > > resources, etc)." > > > > That's why you should reconsider hit. > > > > Frederic > > > > -- > > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
