I promise to let you respond first to the next one ! ;-)

Nico.


> Stop doing that! :-)
> 
> Steve
> 
> > -----Original Message-----
> > From: Nicolas De Loof [mailto:[EMAIL PROTECTED]
> > Sent: July 4, 2003 4:15 AM
> > 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]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to