Re: Why is dbcp / pool removed?

[Ted Husted]

Kruse, Matt wrote:
GenericDataSource now handles all the pooling and stuff itself, instead of
relying on BasicDataSource, which is fine.
But, it also relies on GenericConnection, of which there are two versions -
one for JDK1.3, one for JDK1.4. And the one for JDK1.3 will _not_ compile
JDK1.4. (according to the docs). That's a bummer, because if I release an
app with the 1.3 version packaged in, and the server is upgraded to 1.4, I'm
going to assume that things will break?
If your application does not use 1.4 features, then it shouldn't break. 
We used the 1.3 version because it was compatible both ways.

We only provided the 1.4 version for people who like to compile 
everything themselves.

-Ted.



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

Re: Why is dbcp / pool removed?

[Brendan McCarthy]

Hi Richard,

It seems to have moved into the struts-legacy.jar for RC2. Include it  
in you .war

cheers,
-Brendan
On Thursday, Jun 12, 2003, at 15:57 Australia/Brisbane, Richard Raquepo  
wrote:

I thought GenericDataSource was still included in RC2 or am i wrong? i  
have
remove my old DBCP type datasource and use GenericDataSource but  it  
seems
it does not work too. Am i missing something? Help anyone:
My struts-config.xml datasource is:
  
   
   
   
   
   
   
  
My error is:
1688 [main] ERROR action.ActionServlet  - Initializing application data
source DATASOURCE
java.lang.ClassNotFoundException:  
org.apache.struts.util.GenericDataSource
[java.lang.ClassNotFoundException:  
org.apache.struts.util.GenericDataSource
[java.lang.NoClassDefFoundError:
org/apache/struts/legacy/GenericDataSource]]
at
com.caucho.util.DynamicClassLoader.findClass(DynamicClassLoader.java:56 
9)
at
com.caucho.util.DynamicClassLoader.loadClass(DynamicClassLoader.java:51 
0)
at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
at
org.apache.struts.util.RequestUtils.applicationClass(RequestUtils.java: 
207)
at
org.apache.struts.util.RequestUtils.applicationInstance(RequestUtils.ja 
va:23
1)
at
org.apache.struts.action.ActionServlet.initModuleDataSources(ActionServ 
let.j
ava:1079)
at
org.apache.struts.action.ActionServlet.init(ActionServlet.java:471)
at javax.servlet.GenericServlet.init(GenericServlet.java:82)
at
com.caucho.server.http.Application.createServlet(Application.java:3103)
at
com.caucho.server.http.Application.loadServlet(Application.java:3054)

at
com.caucho.server.http.Application.initServlets(Application.java:1914)
at  
com.caucho.server.http.Application.init(Application.java:1827)
at  
com.caucho.server.http.VirtualHost.init(VirtualHost.java:720)
at
com.caucho.server.http.ServletServer.initHosts(ServletServer.java:853)
at
com.caucho.server.http.ServletServer.initInternal(ServletServer.java:69 
8)
at  
com.caucho.server.http.ServletServer.init(ServletServer.java:509)
at  
com.caucho.server.http.ResinServer.init(ResinServer.java:377)
at  
com.caucho.server.http.ResinServer.main(ResinServer.java:1137)
at com.caucho.server.http.HttpServer.main(HttpServer.java:103)

- Original Message -
From: "Kruse, Matt" <[EMAIL PROTECTED]>
To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
Sent: Tuesday, June 10, 2003 11:12 PM
Subject: RE: Why is dbcp / pool removed?

The one included is not the same as what is in RC1, though,
correct?
I'm not sure what Ted changed but you may be correct that
it's not exactly
the same.  You can still use DBCP, Struts just won't
distribute it any more.
If I move away from DBCP and try to use just the features included  
with
RC2
(for now), it seems like there have been a lot of changes.

GenericDataSource now handles all the pooling and stuff itself,  
instead of
relying on BasicDataSource, which is fine.
But, it also relies on GenericConnection, of which there are two
versions -
one for JDK1.3, one for JDK1.4. And the one for JDK1.3 will _not_  
compile
JDK1.4. (according to the docs). That's a bummer, because if I  
release an
app with the 1.3 version packaged in, and the server is upgraded to  
1.4,
I'm
going to assume that things will break?

I'm not looking for a long-term fix, just a short-term switch to  
possibly
avoid the problems that DBCP might have been causing for me. I'm just
finding it a challenge to figure out which short-term fix to use.

You're not tying your app to the container because you configure the
DataSource implementation entirely in JNDI (my preference) or
struts-config.xml.
In struts-config.xml, if I define my type= to be a container-specific
class,
though, then it's no longer portable. Unless I'm completely
misunderstanding
what you mean, which is likely :)

I'm going to explore "better" ways to handle db connections in the  
future,
but as I said above, I'm just looking for a patch to address current
problems with DBCP, so I want to keep defining my db conns in
struts-config.xml, and I want to rely only on the classes packaged  
with
struts (if possible). I'll experiment and see how it works!

Matt Kruse




-
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]

Re: Why is dbcp / pool removed?

[Richard Raquepo]

I thought GenericDataSource was still included in RC2 or am i wrong? i have
remove my old DBCP type datasource and use GenericDataSource but  it seems
it does not work too. Am i missing something? Help anyone:
>>>>My struts-config.xml datasource is:
  
   
   
   
   
   
   
  
>>>>My error is:
1688 [main] ERROR action.ActionServlet  - Initializing application data
source DATASOURCE
java.lang.ClassNotFoundException: org.apache.struts.util.GenericDataSource
[java.lang.ClassNotFoundException: org.apache.struts.util.GenericDataSource
[java.lang.NoClassDefFoundError:
org/apache/struts/legacy/GenericDataSource]]
at
com.caucho.util.DynamicClassLoader.findClass(DynamicClassLoader.java:569)
at
com.caucho.util.DynamicClassLoader.loadClass(DynamicClassLoader.java:510)
at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
at
org.apache.struts.util.RequestUtils.applicationClass(RequestUtils.java:207)
at
org.apache.struts.util.RequestUtils.applicationInstance(RequestUtils.java:23
1)
at
org.apache.struts.action.ActionServlet.initModuleDataSources(ActionServlet.j
ava:1079)
at
org.apache.struts.action.ActionServlet.init(ActionServlet.java:471)
at javax.servlet.GenericServlet.init(GenericServlet.java:82)
at
com.caucho.server.http.Application.createServlet(Application.java:3103)
at
com.caucho.server.http.Application.loadServlet(Application.java:3054)

at
com.caucho.server.http.Application.initServlets(Application.java:1914)
at com.caucho.server.http.Application.init(Application.java:1827)
at com.caucho.server.http.VirtualHost.init(VirtualHost.java:720)
at
com.caucho.server.http.ServletServer.initHosts(ServletServer.java:853)
at
com.caucho.server.http.ServletServer.initInternal(ServletServer.java:698)
at com.caucho.server.http.ServletServer.init(ServletServer.java:509)
at com.caucho.server.http.ResinServer.init(ResinServer.java:377)
at com.caucho.server.http.ResinServer.main(ResinServer.java:1137)
at com.caucho.server.http.HttpServer.main(HttpServer.java:103)

- Original Message -
From: "Kruse, Matt" <[EMAIL PROTECTED]>
To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
Sent: Tuesday, June 10, 2003 11:12 PM
Subject: RE: Why is dbcp / pool removed?


> > >The one included is not the same as what is in RC1, though,
> > >correct?
> > I'm not sure what Ted changed but you may be correct that
> > it's not exactly
> > the same.  You can still use DBCP, Struts just won't
> > distribute it any more.
>
> If I move away from DBCP and try to use just the features included with
RC2
> (for now), it seems like there have been a lot of changes.
>
> GenericDataSource now handles all the pooling and stuff itself, instead of
> relying on BasicDataSource, which is fine.
> But, it also relies on GenericConnection, of which there are two
versions -
> one for JDK1.3, one for JDK1.4. And the one for JDK1.3 will _not_ compile
> JDK1.4. (according to the docs). That's a bummer, because if I release an
> app with the 1.3 version packaged in, and the server is upgraded to 1.4,
I'm
> going to assume that things will break?
>
> I'm not looking for a long-term fix, just a short-term switch to possibly
> avoid the problems that DBCP might have been causing for me. I'm just
> finding it a challenge to figure out which short-term fix to use.
>
> > You're not tying your app to the container because you configure the
> > DataSource implementation entirely in JNDI (my preference) or
> > struts-config.xml.
>
> In struts-config.xml, if I define my type= to be a container-specific
class,
> though, then it's no longer portable. Unless I'm completely
misunderstanding
> what you mean, which is likely :)
>
> I'm going to explore "better" ways to handle db connections in the future,
> but as I said above, I'm just looking for a patch to address current
> problems with DBCP, so I want to keep defining my db conns in
> struts-config.xml, and I want to rely only on the classes packaged with
> struts (if possible). I'll experiment and see how it works!
>
> Matt Kruse
>
>



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

RE: Why is dbcp / pool removed?

[Phillip Qin]

Off topic, but I like oracle implementation's ability to increase number of
connections automatically. I actually have a factory class return different
pooling data source so that I can switch between dbcp and oracle.

-Original Message-
From: Kris Schneider [mailto:[EMAIL PROTECTED] 
Sent: June 10, 2003 4:19 PM
To: Struts Users Mailing List
Subject: RE: Why is dbcp / pool removed?

If you want to keep your data source config within Struts but don't want to
use
DBCP, it looks like you need to find an alternative implementation of
javax.sql.DataSource. If you're using Oracle for your DB, you might want to
take
a look at oracle.jdbc.pool.OracleConnectionCacheImpl. Other JDBC drivers may
provide something similar.

Quoting "Kruse, Matt" <[EMAIL PROTECTED]>:

> > The Struts distribution no longer includes DBCP but it does 
> > still work with
> > it. You can continue to use DBCP in your app as you did 
> > before. 
> 
> I know :)  But, I was having some problems already that I suspect are due
> to
> that way DBCP is (or isn't!) working, so I did want to replace it with the
> "new" approach in RC2, until I explore JNDI further.
> 
> So, I don't want to use DBCP anymore, but I want to continue using
> struts-config to define my db so as not to disrupt the current state of
the
> app too much. So I'm learning how the DBCP-independent RC2 handles the db
> connections all internally, and trying to figure out if that will work and
> what problems might exist with it. Having some luck so far, but I need to
> do
> a lot more playing around to make sure this doesn't replace my old
problems
> with new ones :)
> 
> Matt
> 


-- 
Kris Schneider <mailto:[EMAIL PROTECTED]>
D.O.Tech   <http://www.dotech.com/>

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

RE: Why is dbcp / pool removed?

[Kris Schneider]

If you want to keep your data source config within Struts but don't want to use
DBCP, it looks like you need to find an alternative implementation of
javax.sql.DataSource. If you're using Oracle for your DB, you might want to take
a look at oracle.jdbc.pool.OracleConnectionCacheImpl. Other JDBC drivers may
provide something similar.

Quoting "Kruse, Matt" <[EMAIL PROTECTED]>:

> > The Struts distribution no longer includes DBCP but it does 
> > still work with
> > it. You can continue to use DBCP in your app as you did 
> > before. 
> 
> I know :)  But, I was having some problems already that I suspect are due
> to
> that way DBCP is (or isn't!) working, so I did want to replace it with the
> "new" approach in RC2, until I explore JNDI further.
> 
> So, I don't want to use DBCP anymore, but I want to continue using
> struts-config to define my db so as not to disrupt the current state of the
> app too much. So I'm learning how the DBCP-independent RC2 handles the db
> connections all internally, and trying to figure out if that will work and
> what problems might exist with it. Having some luck so far, but I need to
> do
> a lot more playing around to make sure this doesn't replace my old problems
> with new ones :)
> 
> Matt
> 


-- 
Kris Schneider 
D.O.Tech   

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

RE: Why is dbcp / pool removed?

[David Graham]

So, I don't want to use DBCP anymore, but I want to continue using
struts-config to define my db so as not to disrupt the current state of the
app too much. So I'm learning how the DBCP-independent RC2 handles the db
connections all internally, and trying to figure out if that will work and
what problems might exist with it. Having some luck so far, but I need to 
do
a lot more playing around to make sure this doesn't replace my old problems
with new ones :)
Just keep in mind that Struts is getting out of the DataSource 
implementation business altogether post 1.1.  You may want to search for 
other connection pooling packages to get a more permanent solution.

David

Matt
_
The new MSN 8: smart spam protection and 2 months FREE*  
http://join.msn.com/?page=features/junkmail

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

RE: Why is dbcp / pool removed?

[Kruse, Matt]

> The Struts distribution no longer includes DBCP but it does 
> still work with
> it. You can continue to use DBCP in your app as you did 
> before. 

I know :)  But, I was having some problems already that I suspect are due to
that way DBCP is (or isn't!) working, so I did want to replace it with the
"new" approach in RC2, until I explore JNDI further.

So, I don't want to use DBCP anymore, but I want to continue using
struts-config to define my db so as not to disrupt the current state of the
app too much. So I'm learning how the DBCP-independent RC2 handles the db
connections all internally, and trying to figure out if that will work and
what problems might exist with it. Having some luck so far, but I need to do
a lot more playing around to make sure this doesn't replace my old problems
with new ones :)

Matt

RE: Why is dbcp / pool removed?

[Steve Raeburn]

> I'm not looking for a long-term fix, just a short-term switch to possibly
> avoid the problems that DBCP might have been causing for me. I'm just
> finding it a challenge to figure out which short-term fix to use.
>
> Matt Kruse

Matt,

The Struts distribution no longer includes DBCP but it does still work with
it. You can continue to use DBCP in your app as you did before. You can
specify the implementation class on the data-source tag in struts-config:
  
...
  

You also need to make sure you've got the correct jars in your lib
directory. (commons-dbcp.jar, commons-pool.jar - there may be others, I'm
not sure of the exact dependency of DBCP).

So, in the short term you need do nothing except make a small change to
struts-config.xml. In the longer term you could investigate the options,
such as JNDI, that others have suggested - but you won't be forced to change
unless it suits you.

Steve


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

Re: Why is dbcp / pool removed?

[David Graham]

http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jndi-datasource-examples-howto.html

David

Ed Yu wrote:
You are better off using JNDI lookup to get the datasource. This is
suppose to be universal (Tomcat and Jrun seems to work identical)
although I've found a couple of differences among containers.
Do you know of a decent how-to document on designs to use this method 
rather than directly use DBCP

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
_
Help STOP SPAM with the new MSN 8 and get 2 months FREE*  
http://join.msn.com/?page=features/junkmail

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

Re: Why is dbcp / pool removed?

[Erik Price]

Ed Yu wrote:
You are better off using JNDI lookup to get the datasource. This is
suppose to be universal (Tomcat and Jrun seems to work identical)
although I've found a couple of differences among containers.
Do you know of a decent how-to document on designs to use this method 
rather than directly use DBCP

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

RE: Why is dbcp / pool removed?

[Ed Yu]

You are better off using JNDI lookup to get the datasource. This is
suppose to be universal (Tomcat and Jrun seems to work identical)
although I've found a couple of differences among containers.

^^ 
Ed Yu, Senior Solutions Architect (IBM Certified AIX Administrator), 
Advanced Solutions Group, Physics Dept., University of South Carolina,
Columbia, SC 29208 
Office (803)777-8831, FAX (803)777-8833, Email [EMAIL PROTECTED]


> -Original Message-
> From: Kruse, Matt [mailto:[EMAIL PROTECTED] 
> Sent: Tuesday, June 10, 2003 11:13 AM
> To: Struts Users Mailing List
> Subject: RE: Why is dbcp / pool removed?
> 
> 
> > >The one included is not the same as what is in RC1, though,
> > >correct? 
> > I'm not sure what Ted changed but you may be correct that
> > it's not exactly 
> > the same.  You can still use DBCP, Struts just won't 
> > distribute it any more.
> 
> If I move away from DBCP and try to use just the features 
> included with RC2 (for now), it seems like there have been a 
> lot of changes.
> 
> GenericDataSource now handles all the pooling and stuff 
> itself, instead of relying on BasicDataSource, which is fine. 
> But, it also relies on GenericConnection, of which there are 
> two versions - one for JDK1.3, one for JDK1.4. And the one 
> for JDK1.3 will _not_ compile JDK1.4. (according to the 
> docs). That's a bummer, because if I release an app with the 
> 1.3 version packaged in, and the server is upgraded to 1.4, 
> I'm going to assume that things will break?
> 
> I'm not looking for a long-term fix, just a short-term switch 
> to possibly avoid the problems that DBCP might have been 
> causing for me. I'm just finding it a challenge to figure out 
> which short-term fix to use.
> 
> > You're not tying your app to the container because you configure the
> > DataSource implementation entirely in JNDI (my preference) or 
> > struts-config.xml.
> 
> In struts-config.xml, if I define my type= to be a 
> container-specific class, though, then it's no longer 
> portable. Unless I'm completely misunderstanding what you 
> mean, which is likely :)
> 
> I'm going to explore "better" ways to handle db connections 
> in the future, but as I said above, I'm just looking for a 
> patch to address current problems with DBCP, so I want to 
> keep defining my db conns in struts-config.xml, and I want to 
> rely only on the classes packaged with struts (if possible). 
> I'll experiment and see how it works!
> 
> Matt Kruse
> 
> 

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

RE: Why is dbcp / pool removed?

[Kruse, Matt]

> >The one included is not the same as what is in RC1, though, 
> >correct? 
> I'm not sure what Ted changed but you may be correct that 
> it's not exactly 
> the same.  You can still use DBCP, Struts just won't 
> distribute it any more.

If I move away from DBCP and try to use just the features included with RC2
(for now), it seems like there have been a lot of changes.

GenericDataSource now handles all the pooling and stuff itself, instead of
relying on BasicDataSource, which is fine.
But, it also relies on GenericConnection, of which there are two versions -
one for JDK1.3, one for JDK1.4. And the one for JDK1.3 will _not_ compile
JDK1.4. (according to the docs). That's a bummer, because if I release an
app with the 1.3 version packaged in, and the server is upgraded to 1.4, I'm
going to assume that things will break?

I'm not looking for a long-term fix, just a short-term switch to possibly
avoid the problems that DBCP might have been causing for me. I'm just
finding it a challenge to figure out which short-term fix to use.

> You're not tying your app to the container because you configure the 
> DataSource implementation entirely in JNDI (my preference) or 
> struts-config.xml.

In struts-config.xml, if I define my type= to be a container-specific class,
though, then it's no longer portable. Unless I'm completely misunderstanding
what you mean, which is likely :)

I'm going to explore "better" ways to handle db connections in the future,
but as I said above, I'm just looking for a patch to address current
problems with DBCP, so I want to keep defining my db conns in
struts-config.xml, and I want to rely only on the classes packaged with
struts (if possible). I'll experiment and see how it works!

Matt Kruse

RE: Why is dbcp / pool removed?

[David Graham]

Is there a list of the problems that DBCP has?  I've started using the
BasicDataSource in some of my applications, and am wondering if some of the
really wierd behaviour I'm seeing is due to the problems that DBCP has
Search bugzilla for open problem tickets.

David

Thanks.

Jerry Jalenak
Team Lead, Web Publishing
LabOne, Inc.
10101 Renner Blvd.
Lenexa, KS  66219
(913) 577-1496
[EMAIL PROTECTED]

-Original Message-
From: Kruse, Matt [mailto:[EMAIL PROTECTED]
Sent: Monday, June 09, 2003 11:50 PM
To: '[EMAIL PROTECTED] '
Subject: RE: Why is dbcp / pool removed?
>Isn't GenericDataSource deprecated?
>Yes, it will be removed in 1.2 but is included in
>1.1 for backward compatibility.
The one included is not the same as what is in RC1, though, correct? I'm
just trying to figure out exactly what is changed and what I need to start
experimenting with...
> I recommend using the package distributed with either your
> container or your database.
If you tie your app to your coontainer, then it's not very portable, no? I
can develop in Tomcat and publish to JRun with no problems, and I like to
maintain that :)
I suppose for now a good plan would be to use GenericDataSource and 
research
more reliable and portable options for conn pooling in the future? Perhaps
by then DBCP will be cleaned up and a good stand-alone alternative.

Matt Kruse

This transmission (and any information attached to it) may be confidential 
and is intended solely for the use of the individual or entity to which it 
is addressed. If you are not the intended recipient or the person 
responsible for delivering the transmission to the intended recipient, be 
advised that you have received this transmission in error and that any use, 
dissemination, forwarding, printing, or copying of this information is 
strictly prohibited. If you have received this transmission in error, 
please immediately notify LabOne at the following email address: 
[EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
_
Protect your PC - get McAfee.com VirusScan Online  
http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963

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

RE: Why is dbcp / pool removed?

[Jerry Jalenak]

Is there a list of the problems that DBCP has?  I've started using the
BasicDataSource in some of my applications, and am wondering if some of the
really wierd behaviour I'm seeing is due to the problems that DBCP has

Thanks.

Jerry Jalenak
Team Lead, Web Publishing
LabOne, Inc.
10101 Renner Blvd.
Lenexa, KS  66219
(913) 577-1496

[EMAIL PROTECTED]


-Original Message-
From: Kruse, Matt [mailto:[EMAIL PROTECTED]
Sent: Monday, June 09, 2003 11:50 PM
To: '[EMAIL PROTECTED] '
Subject: RE: Why is dbcp / pool removed?


>Isn't GenericDataSource deprecated?
>Yes, it will be removed in 1.2 but is included in 
>1.1 for backward compatibility.

The one included is not the same as what is in RC1, though, correct? I'm
just trying to figure out exactly what is changed and what I need to start
experimenting with...

> I recommend using the package distributed with either your 
> container or your database.

If you tie your app to your coontainer, then it's not very portable, no? I
can develop in Tomcat and publish to JRun with no problems, and I like to
maintain that :)

I suppose for now a good plan would be to use GenericDataSource and research
more reliable and portable options for conn pooling in the future? Perhaps
by then DBCP will be cleaned up and a good stand-alone alternative.

Matt Kruse

This transmission (and any information attached to it) may be confidential and is 
intended solely for the use of the individual or entity to which it is addressed. If 
you are not the intended recipient or the person responsible for delivering the 
transmission to the intended recipient, be advised that you have received this 
transmission in error and that any use, dissemination, forwarding, printing, or 
copying of this information is strictly prohibited. If you have received this 
transmission in error, please immediately notify LabOne at the following email 
address: [EMAIL PROTECTED]



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

RE: Why is dbcp / pool removed?

[Bradley M. Handy]

I use a data persistence library called "Hibernate" 
(http://hibernate.bluemars.net).  Hibernate comes with two connection 
pooling libraries:  (1) DBCP, which I haven't used, because I didn't want 
to do the extra configuration, and (2) it's own home grown pooling library 
called c3p0.  I've just started using it in my applications, and I haven't 
had much of a problem with it.

Brad Handy

At 09:39 AM 6/10/2003, you wrote:
>Isn't GenericDataSource deprecated?
>Yes, it will be removed in 1.2 but is included in
>1.1 for backward compatibility.
The one included is not the same as what is in RC1, though, correct? I'm
just trying to figure out exactly what is changed and what I need to start
experimenting with...
I'm not sure what Ted changed but you may be correct that it's not exactly 
the same.  You can still use DBCP, Struts just won't distribute it any more.

> I recommend using the package distributed with either your
> container or your database.
If you tie your app to your coontainer, then it's not very portable, no? I
can develop in Tomcat and publish to JRun with no problems, and I like to
maintain that :)
You're not tying your app to the container because you configure the 
DataSource implementation entirely in JNDI (my preference) or 
struts-config.xml.

David

I suppose for now a good plan would be to use GenericDataSource and research
more reliable and portable options for conn pooling in the future? Perhaps
by then DBCP will be cleaned up and a good stand-alone alternative.
Matt Kruse
_
The new MSN 8: smart spam protection and 2 months FREE*
http://join.msn.com/?page=features/junkmail
-
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]

RE: Why is dbcp / pool removed?

[David Graham]

>Isn't GenericDataSource deprecated?
>Yes, it will be removed in 1.2 but is included in
>1.1 for backward compatibility.
The one included is not the same as what is in RC1, though, correct? I'm
just trying to figure out exactly what is changed and what I need to start
experimenting with...
I'm not sure what Ted changed but you may be correct that it's not exactly 
the same.  You can still use DBCP, Struts just won't distribute it any more.

> I recommend using the package distributed with either your
> container or your database.
If you tie your app to your coontainer, then it's not very portable, no? I
can develop in Tomcat and publish to JRun with no problems, and I like to
maintain that :)
You're not tying your app to the container because you configure the 
DataSource implementation entirely in JNDI (my preference) or 
struts-config.xml.

David

I suppose for now a good plan would be to use GenericDataSource and 
research
more reliable and portable options for conn pooling in the future? Perhaps
by then DBCP will be cleaned up and a good stand-alone alternative.

Matt Kruse
_
The new MSN 8: smart spam protection and 2 months FREE*  
http://join.msn.com/?page=features/junkmail

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

RE: Why is dbcp / pool removed?

[Ed Yu]

Actually, the recommended way is to use JNDI to accquire a data source from the 
container. Most container supports it.

-Original Message- 
From: Kruse, Matt [mailto:[EMAIL PROTECTED] 
Sent: Tue 06/10/2003 0:49 
To: '[EMAIL PROTECTED] ' 
Cc: 
    Subject: RE: Why is dbcp / pool removed?



>Isn't GenericDataSource deprecated?
>Yes, it will be removed in 1.2 but is included in
>1.1 for backward compatibility.

The one included is not the same as what is in RC1, though, correct? I'm
just trying to figure out exactly what is changed and what I need to start
experimenting with...

> I recommend using the package distributed with either your
> container or your database.

If you tie your app to your coontainer, then it's not very portable, no? I
can develop in Tomcat and publish to JRun with no problems, and I like to
maintain that :)

I suppose for now a good plan would be to use GenericDataSource and research
more reliable and portable options for conn pooling in the future? Perhaps
by then DBCP will be cleaned up and a good stand-alone alternative.

Matt Kruse


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

RE: Why is dbcp / pool removed?

[Kruse, Matt]

>Isn't GenericDataSource deprecated?
>Yes, it will be removed in 1.2 but is included in 
>1.1 for backward compatibility.

The one included is not the same as what is in RC1, though, correct? I'm
just trying to figure out exactly what is changed and what I need to start
experimenting with...

> I recommend using the package distributed with either your 
> container or your database.

If you tie your app to your coontainer, then it's not very portable, no? I
can develop in Tomcat and publish to JRun with no problems, and I like to
maintain that :)

I suppose for now a good plan would be to use GenericDataSource and research
more reliable and portable options for conn pooling in the future? Perhaps
by then DBCP will be cleaned up and a good stand-alone alternative.

Matt Kruse

RE: Why is dbcp / pool removed?

[Brandon Goodin]

DBCP.

Brandon Goodin 

-Original Message-
From: Richard Raquepo [mailto:[EMAIL PROTECTED]
Sent: Monday, June 09, 2003 9:58 PM
To: Struts Users Mailing List
Subject: Re: Why is dbcp / pool removed?


im using tomcat. what is included in tomcat then?
thanks.

> I recommend using the package distributed with either your container or
your
> database.
>
> David

- Original Message -
From: "David Graham" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, June 10, 2003 11:07 AM
Subject: RE: Why is dbcp / pool removed?


> > >Struts 1.1 includes its trusty old GenericDataSource but you
> > >can always plugin DBCP if you want.
> >
> >Hold on a second...
> >
> >Isn't GenericDataSource deprecated?
>
> Yes, it will be removed in 1.2 but is included in 1.1 for backward
> compatibility.
>
> >I just recently switched from using
> >GenericDataSource in my struts-config.xml (by specifying no type=) to
> >explicitly using type=org.apache.commons.dbcp.BasicDataSource because of
> >the
> >docs in GenericDataSource. Is this no longer the recommended approach?
>
> If DBCP works for you, then continue using it.  It's just not included in
> the Struts distro anymore.  In the future Struts won't distribute *any*
> connection pooling package, you will have to plug in your favorite
> implementation.
>
> >
> >Currently, I'm having some problems with pooling and idle connections
which
> >are closed by the db server actually being given back to my app (I
> >suspect).
> >Could this be related to the bugs in dbcp you are talking about?
>
> Maybe, this behavior is configurable in DBCP so it may or may not be
trying
> to recover lost connections.
>
> >
> >Using 1.1RC2, what is the recommended way to acquire pooled db
connections?
>
> I recommend using the package distributed with either your container or
your
> database.
>
> David
>
> >
> >Matt Kruse
>
> _
> Add photos to your messages with MSN 8. Get 2 months FREE*.
> http://join.msn.com/?page=features/featuredemail
>
>
> -
> 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]

Re: Why is dbcp / pool removed?

[David Graham]

im using tomcat. what is included in tomcat then?
thanks.
Tomcat uses DBCP.  Interestingly, no one from Tomcat seems interested in 
maintaining DBCP.

David

> I recommend using the package distributed with either your container or
your
> database.
>
> David
- Original Message -
From: "David Graham" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, June 10, 2003 11:07 AM
Subject: RE: Why is dbcp / pool removed?
> > >Struts 1.1 includes its trusty old GenericDataSource but you
> > >can always plugin DBCP if you want.
> >
> >Hold on a second...
> >
> >Isn't GenericDataSource deprecated?
>
> Yes, it will be removed in 1.2 but is included in 1.1 for backward
> compatibility.
>
> >I just recently switched from using
> >GenericDataSource in my struts-config.xml (by specifying no type=) to
> >explicitly using type=org.apache.commons.dbcp.BasicDataSource because 
of
> >the
> >docs in GenericDataSource. Is this no longer the recommended approach?
>
> If DBCP works for you, then continue using it.  It's just not included 
in
> the Struts distro anymore.  In the future Struts won't distribute *any*
> connection pooling package, you will have to plug in your favorite
> implementation.
>
> >
> >Currently, I'm having some problems with pooling and idle connections
which
> >are closed by the db server actually being given back to my app (I
> >suspect).
> >Could this be related to the bugs in dbcp you are talking about?
>
> Maybe, this behavior is configurable in DBCP so it may or may not be
trying
> to recover lost connections.
>
> >
> >Using 1.1RC2, what is the recommended way to acquire pooled db
connections?
>
> I recommend using the package distributed with either your container or
your
> database.
>
> David
>
> >
> >Matt Kruse
>
> _
> Add photos to your messages with MSN 8. Get 2 months FREE*.
> http://join.msn.com/?page=features/featuredemail
>
>
> -
> 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]
_
Protect your PC - get McAfee.com VirusScan Online  
http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963

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

Re: Why is dbcp / pool removed?

[Richard Raquepo]

im using tomcat. what is included in tomcat then?
thanks.

> I recommend using the package distributed with either your container or
your
> database.
>
> David

- Original Message -
From: "David Graham" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, June 10, 2003 11:07 AM
Subject: RE: Why is dbcp / pool removed?


> > >Struts 1.1 includes its trusty old GenericDataSource but you
> > >can always plugin DBCP if you want.
> >
> >Hold on a second...
> >
> >Isn't GenericDataSource deprecated?
>
> Yes, it will be removed in 1.2 but is included in 1.1 for backward
> compatibility.
>
> >I just recently switched from using
> >GenericDataSource in my struts-config.xml (by specifying no type=) to
> >explicitly using type=org.apache.commons.dbcp.BasicDataSource because of
> >the
> >docs in GenericDataSource. Is this no longer the recommended approach?
>
> If DBCP works for you, then continue using it.  It's just not included in
> the Struts distro anymore.  In the future Struts won't distribute *any*
> connection pooling package, you will have to plug in your favorite
> implementation.
>
> >
> >Currently, I'm having some problems with pooling and idle connections
which
> >are closed by the db server actually being given back to my app (I
> >suspect).
> >Could this be related to the bugs in dbcp you are talking about?
>
> Maybe, this behavior is configurable in DBCP so it may or may not be
trying
> to recover lost connections.
>
> >
> >Using 1.1RC2, what is the recommended way to acquire pooled db
connections?
>
> I recommend using the package distributed with either your container or
your
> database.
>
> David
>
> >
> >Matt Kruse
>
> _
> Add photos to your messages with MSN 8. Get 2 months FREE*.
> http://join.msn.com/?page=features/featuredemail
>
>
> -
> 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]

RE: Why is dbcp / pool removed?

[David Graham]

>Struts 1.1 includes its trusty old GenericDataSource but you
>can always plugin DBCP if you want.
Hold on a second...

Isn't GenericDataSource deprecated?
Yes, it will be removed in 1.2 but is included in 1.1 for backward 
compatibility.

I just recently switched from using
GenericDataSource in my struts-config.xml (by specifying no type=) to
explicitly using type=org.apache.commons.dbcp.BasicDataSource because of 
the
docs in GenericDataSource. Is this no longer the recommended approach?
If DBCP works for you, then continue using it.  It's just not included in 
the Struts distro anymore.  In the future Struts won't distribute *any* 
connection pooling package, you will have to plug in your favorite 
implementation.

Currently, I'm having some problems with pooling and idle connections which
are closed by the db server actually being given back to my app (I 
suspect).
Could this be related to the bugs in dbcp you are talking about?
Maybe, this behavior is configurable in DBCP so it may or may not be trying 
to recover lost connections.

Using 1.1RC2, what is the recommended way to acquire pooled db connections?
I recommend using the package distributed with either your container or your 
database.

David

Matt Kruse
_
Add photos to your messages with MSN 8. Get 2 months FREE*.  
http://join.msn.com/?page=features/featuredemail

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

Re: Why is dbcp / pool removed?

[Vic Cekvenich]

The idea is that people should use the container's (application 
server's) connection pool, since each container has one, it's not a core 
Struts value.
.V



Kruse, Matt wrote:

Struts 1.1 includes its trusty old GenericDataSource but you 
can always plugin DBCP if you want.
   

Hold on a second...

Isn't GenericDataSource deprecated? I just recently switched from using
GenericDataSource in my struts-config.xml (by specifying no type=) to
explicitly using type=org.apache.commons.dbcp.BasicDataSource because of the
docs in GenericDataSource. Is this no longer the recommended approach?
Currently, I'm having some problems with pooling and idle connections which
are closed by the db server actually being given back to my app (I suspect).
Could this be related to the bugs in dbcp you are talking about?
Using 1.1RC2, what is the recommended way to acquire pooled db connections?

Matt Kruse

 

--
Vic Cekvenich,
Struts Instructor,
1-800-917-JAVA
Advanced Struts Training and project recovery in North 
East.
Open Source Content Management  basicPortal sofware
Best practiceStruts Support v.1.1 helper ScafflodingXPress

RE: Why is dbcp / pool removed?

[Kruse, Matt]

>Struts 1.1 includes its trusty old GenericDataSource but you 
>can always plugin DBCP if you want.

Hold on a second...

Isn't GenericDataSource deprecated? I just recently switched from using
GenericDataSource in my struts-config.xml (by specifying no type=) to
explicitly using type=org.apache.commons.dbcp.BasicDataSource because of the
docs in GenericDataSource. Is this no longer the recommended approach?

Currently, I'm having some problems with pooling and idle connections which
are closed by the db server actually being given back to my app (I suspect).
Could this be related to the bugs in dbcp you are talking about?

Using 1.1RC2, what is the recommended way to acquire pooled db connections?

Matt Kruse

Re: Why is dbcp / pool removed?

[David Graham]

Just wondering why dbcp/pool is removed from RC2, will they be back for the 
final release?  I have lots of apps that use them and wanted to know what 
direction this is going.
Because no one was willing to fix DBCP.  It's really a one man show over 
there and he was busy doing other things.  I took a crack at it and 
determined the problems (such as trying to recover lost connections from 
poorly coded apps) ran too deep to fix in a suitable amount of time.  Struts 
1.1 includes its trusty old GenericDataSource but you can always plugin DBCP 
if you want.

David

Thanks
Ka-Wai


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
_
STOP MORE SPAM with the new MSN 8 and get 2 months FREE*  
http://join.msn.com/?page=features/junkmail

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

RE: Why is dbcp / pool removed?

[Brandon Goodin]

It has been removed permanently. The dbcp/pool has several unresolved bugs
that weren't getting fixed and in turn were impeding the release of rc2.

Brandon Goodin

-Original Message-
From: Ka-Wai Chan [mailto:[EMAIL PROTECTED]
Sent: Monday, June 09, 2003 5:11 PM
To: [EMAIL PROTECTED]
Subject: Why is dbcp / pool removed?


Hello

Just wondering why dbcp/pool is removed from RC2, will they be back for
the final release?  I have lots of apps that use them and wanted to know
what direction this is going.

Thanks
Ka-Wai



-
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]