Women in Technology

Article:		SQL Database Access with DBTags
Subject:		better alternatives
Date:		2004-05-07 02:45:27
From:		jwenting
Response to: better alternatives
I'd contest your "it is from Jakarta which means it's probably not of production quality". The Jakarta project has turned out quite a bit of code that's very much of production quality. Tomcat (4.1 and 5 at least) is just one example and is recognised by Sun as the reference implementation for the Servlet and JSP platform. Their JSTL implementation is just about the industry standard. Xalan and Xerces are related closely to Jakarta and are again industry standards. The list goes on... I DO agree that using JSTL instead of the Jakarta specific tags is a good idea. I would not be surprised if those libraries which show duplicate functionality from the JSTL will in time be dropped from the Jakarta project. As is stated on the Jakarta site Over time, some projects are deprecated because their functionality is covered by JCP standardized tag libraries, or because newer, improved projects supersede them. Deprecated tag libraries can be accessed here. (the SQL tags are not yet among these).

Showing messages 1 through 2 of 2.

• better alternatives
  2004-07-07 06:54:20  Deepak Vohra | [View]
  
  
  I would like to add from the DBTags documentation:
  
  Although JSTL and DBTags contain similar functionality, some users may find the JSTL usage a little daunting. For this reason, DBTags will still remain as an alternative to the JSTL tags.

• better alternatives
  2004-05-07 02:47:41  jwenting [View]
  
  
  it does however state clearly: If you are using a recent implementation of the Servlet specification, you should use Jakarta's Standard, which is an implementation of JSTL, not DBTags.
  DBTags has been pretty much inactive since development on JSTL began, and it should be considered deprecated for Servlet 2.3 or 2.4 containers.
  For more information about the DBTags/JSTL relationship, check the old DBTags State of the Union document.