juddi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andy Cutright" <Andy.Cutri...@borland.com>
Subject RE: [juddi-Developers] ConnectionPool replaced with Jakarta Commo ns DBCP
Date Fri, 19 Sep 2003 13:07:04 GMT
yeah, this was supposed to be fixed by august time frame.. 

http://sourceforge.net/docman/display_doc.php?docid=17790&group_id=1#cvs

i suppose it's pointless to submit a bug to them.. 	

cheers,
andy 

> -----Original Message-----
> From: Steve Viens [mailto:steve@viens.net] 
> Sent: Thursday, September 18, 2003 5:17 PM
> To: juddi-developers@lists.sourceforge.net
> Subject: RE: [juddi-Developers] ConnectionPool replaced with 
> Jakarta Commo ns DBCP
> 
> 
> I agree ... they said they were planning to fix that last month.
> 
> Steve
> 
> -----Original Message-----
> From: juddi-developers-admin@lists.sourceforge.net
> [mailto:juddi-developers-admin@lists.sourceforge.net] On Behalf Of
> mcuenca2@matiascuenca.com.ar
> Sent: Thursday, September 18, 2003 7:22 PM
> To: juddi-developers@lists.sourceforge.net
> Subject: RE: [juddi-Developers] ConnectionPool replaced with Jakarta
> Commo ns DBCP
> 
> 
> 	I have also checked out all the code again and I still have the
> new pool jars missing from the war file. Sourceforge's CVS service is
> terrible (at least for anonymous users)!!!
> 
> 	Here is what I get when I do status
> 		
> 		Matias
> 
> [mcuenca@x juddi]$ cvs -z3
> -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/juddi status -v
> build.xml                                        
> ===================================================================
> File: build.xml         Status: Up-to-date
> 
>    Working revision:    1.22
>    Repository revision: 1.22    /cvsroot/juddi/juddi/build.xml,v
>    Sticky Tag:          (none)
>    Sticky Date:         (none)
>    Sticky Options:      (none)
> 
>    Existing Tags:
>         juddi_0_8_0                     (revision: 1.1.1.1)
>         vendor                          (branch: 1.1.1)
> 
> 
> On Thu, 18 Sep 2003, Viens, Steve wrote:
> 
> > Really? It should ... could you double check that you've got the 
> > latest build.xml?
> >  
> > Steve
> > 
> > -----Original Message-----
> > From: Andy Cutright [mailto:Andy.Cutright@borland.com]
> > Sent: Thursday, September 18, 2003 1:25 PM
> > To: juddi-developers@lists.sourceforge.net
> > Subject: RE: [juddi-Developers] ConnectionPool replaced with Jakarta
> Commons
> > DBCP
> > 
> > 
> > the build.xml doesn't jar these up into the .war, causing 
> the error i 
> > was getting earlier: class not found.
> >  
> > cheers,
> > andy
> >  
> > -----Original Message-----
> > From: Steve Viens [mailto:steve@viens.net]
> > Sent: Wednesday, September 17, 2003 7:28 PM
> > To: juddi-developers@lists.sourceforge.net
> > Cc: 'Francisco Matias Cuenca-Acuna'
> > Subject: [juddi-Developers] ConnectionPool replaced with Jakarta
> Commons
> > DBCP
> > 
> > 
> > 
> > fyi,
> >  
> > I've removed the ConnectionPool class from jUDDI and replaced the 
> > functionality it was used for with the Jakarta Commons DBCP package 
> > (http://jakarta.apache.org/commons/dbcp/
> > <http://jakarta.apache.org/commons/dbcp/> ).  
> ConnectionPool and now 
> > DBCP are typically used when the ability to lookup a DataSource 
> > through JNDI is not available.
> >  
> > This change added three new jar files to jUDDI:
> >  
> >   commons-collections.jar (version 2.1)
> >   commons-dbcp.jar (version 1.0)
> >   commons-pool.jar (version 1.0.1)
> >  
> > The properties (in juddi.properties) used by jUDDI to setup 
> the DBCP 
> > connection pool are largely the same as those used by the old 
> > ConnectionPool class.  Here are the values specified in 
> > juddi.properties (these are also the default values used by 
> jUDDI if 
> > they're not found in juddi.properties.)
> >  
> >   juddi.useConnectionPool=false
> >   juddi.jdbcDriver=com.mysql.jdbc.Driver
> >   juddi.jdbcURL=jdbc:mysql://localhost/juddi
> >   juddi.jdbcUser=juddi
> >   juddi.jdbcPassword=juddi
> >   juddi.jdbcMaxActive=10
> >   juddi.jdbcMaxIdle=10
> > 
> > To use DBCP connection pooling instead of JNDI simply set 
> > juddi.useConnectionPool value to "true".
> >  
> > The juddi.jdbcMaxActive and juddi.jdbcMaxIdle properties are new 
> > (actually, they're simply renamed from juddi.jdbcMaxConnections and 
> > jddi.jdbcMinConnections respectively).  These were option 
> properties 
> > in ConnectionPool.  Also, the optional juddi.jdbcMaxWaitTime and 
> > juddi.jdbcRetryInterval properties specify values that are 
> not used by
> 
> > DBCP.
> >  
> > Steve
> > steve@viens.net <mailto:steve@viens.net>
> > 
> > 
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf 
> _______________________________________________
> juddi-developers mailing list juddi-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/juddi-developers
> 
> 
> 
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> juddi-developers mailing list
> juddi-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/juddi-developers
> 


Mime
View raw message