http://issues.apache.org/bugzilla/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&bugidtype=include&bug_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&product=Commons&component=Dbcp&short_desc=&short_desc_type=allwordssubstr&long_desc=&long_desc_type=allwordssubstr&bug_file_loc=&bug_file_loc_type=allwordssubstr&keywords=&keywords_type=anywords&field0-0-0=noop&type0-0-0=noop&value0-0-0=&cmdtype=doit&order=Reuse+same+sort+as+last+time
seems like they're still a few issues there to clear up.
David Bolsover wrote:
Nico /Steve
Thanks for the prompt replies - glad I stuck with GenericDataSource rather than trying out the commons-dbpc offerings!
db
-----Original Message----- From: Nicolas De Loof [mailto:[EMAIL PROTECTED] Sent: 04 July 2003 12:15 To: Struts Users Mailing List; [EMAIL PROTECTED] Subject: Re: GenericDataSource
Struts 1.1 has dependencies to some commons projects. First 1.1 pre-release of Struts used commons-dbcp for the DataSource functionnality in replacement of GenericDataSource .
Waiting for this commons to get stable before releasing 1.1 final, Struts commiters agreed to go back to GenericDataSource because commons-dbcp looked very unstable.
Struts-legacy has been created to include this class outside of Struts core as DefaultDataSource have been deprecated : Future Struts version will set the <datasource> "type" attribute to mandatory, so you will have to set your selected DataSource (that can be commons-dbcp, and lot's of us use container pool service and JNDI to get a DataSource).
Nico.
Can someone explain why GenericDataSource was moved to lagacy?
I have been using it successfully as a JINI DataSourse - have others
experienced
problems? - if so, what problems?
db
--------------------------------------------------------------------- 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]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
