You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by Edgar P Dollin <ed...@blue-moose.net> on 2003/12/03 23:03:23 UTC
RE: Should Struts ship with all of the commons jar files needed t
o get Struts datasources working?
I disagree about the web app containing the DB Pool as configuration of
multiple DB Pools in a container containing many different apps is a royal
pain, not to mention a potential source of downtime for unrelated users.
Please don't remove this feature. Leave it depreated as long as you like.
Thanks
Edgar
-----Original Message-----
From: Vic Cekvenich [mailto:cekvenich_vic@basebeans.com]
Sent: Wednesday, December 03, 2003 4:43 PM
To: struts-dev@jakarta.apache.org
Subject: Re: Should Struts ship with all of the commons jar files needed
to get Struts datasources working?
Hello Rick,
They are deprecated; targeted for removal; and for a good reason, since
it's a bad practice to have a data source served by the web app., a
container provides a data source. In esence, maybe legacy jar should not
be included any more, it has been a while since 1.1 released.
There is to much talk about data connection's as it is on user.
(I wish more be taged as deprected :logic/bean, since in the future...
they will be and there was a comment on dev list that no one is keen to
patch, so just give users a signal )
.V
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org
RE: Should Struts ship with all of the commons jar files needed to get Struts datasources working?
Posted by Rick Hightower <rh...@triveratech.com>.
Ya know. I was just starting to warm up to the idea for that very reason. It
is a pain to configure DB connection pools for every app server.
-----Original Message-----
From: Edgar P Dollin [mailto:edgar@blue-moose.net]
Sent: Wednesday, December 03, 2003 2:03 PM
To: 'Struts Developers List'
Subject: RE: Should Struts ship with all of the commons jar files needed to
get Struts datasources working?
I disagree about the web app containing the DB Pool as configuration of
multiple DB Pools in a container containing many different apps is a royal
pain, not to mention a potential source of downtime for unrelated users.
Please don't remove this feature. Leave it depreated as long as you like.
Thanks
Edgar
-----Original Message-----
From: Vic Cekvenich [mailto:cekvenich_vic@basebeans.com]
Sent: Wednesday, December 03, 2003 4:43 PM
To: struts-dev@jakarta.apache.org
Subject: Re: Should Struts ship with all of the commons jar files needed
to get Struts datasources working?
Hello Rick,
They are deprecated; targeted for removal; and for a good reason, since
it's a bad practice to have a data source served by the web app., a
container provides a data source. In esence, maybe legacy jar should not
be included any more, it has been a while since 1.1 released.
There is to much talk about data connection's as it is on user.
(I wish more be taged as deprected :logic/bean, since in the future...
they will be and there was a comment on dev list that no one is keen to
patch, so just give users a signal )
.V
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org