.
-Original Message-
From: Michal Postupalski [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, February 12, 2003 5:55 PM
To: Struts Users Mailing List
Subject: Re: [newbie] Connection Pooling
On 2/12/2003 11:20 PM, Guido wrote:
IMHO, storing the connection in the session context is *never* a good
Folks,
quite new to Struts and it's way to JPS-Action-etc. chaining I'd like to
know the following. Is their a way to keep open a certain connection to
a database between two actions, e.g. I have a EditGetAction where I
prepopulate a form, then show the jsp and make the user work and finally
-
From: Andre Michel [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, February 12, 2003 3:53 PM
To: Struts Users Mailing List
Subject: [newbie] Connection Pooling
Folks,
quite new to Struts and it's way to JPS-Action-etc. chaining I'd like to
know the following. Is their a way to keep open
To: Struts Users Mailing List
Subject: [newbie] Connection Pooling
Folks,
quite new to Struts and it's way to JPS-Action-etc. chaining I'd like to
know the following. Is their a way to keep open a certain connection to a
database between two actions, e.g. I have a EditGetAction where I
You can configure a DataSource in the struts-config.xml file that will
return connections to you. You should not keep the connection open longer
than needed and this means you shouldn't span action invocations.
David
Folks,
quite new to Struts and it's way to JPS-Action-etc. chaining I'd
to the pool as soon as
you're done with them.
-- los
-Original Message-
From: Marco Tedone [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, February 12, 2003 4:35 PM
To: Struts-user-list
Subject: RE: [newbie] Connection Pooling
You could write a PlugIn(new to Struts 1.1) to open a db
On 2/12/2003 10:34 PM, Marco Tedone wrote:
You could write a PlugIn(new to Struts 1.1) to open a db connection and
store it in the session context. I would remember to close it in the
destroy() method.
Only an idea.
Yes, it's a good idea. I use it sometimes but only when I have only one
IMHO, storing the connection in the session context is *never* a good
idea!
1. Session timeout uses to be too high if you must wait the session to
expire to close your connection (the user closes the browser...)
2. You can kill your DB or you app server... And think about how many
connections
100% agree. The only thing that should be placed in a session is user
specific stuff. Connections should never be user specific, connections
should be returned to the pool so other users can have them when they
need it. The thing is that before such cool methodologies you had to
buy
Yes, so do I. :-)
Marco
-Original Message-
From: Micha³ Postupalski [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, February 12, 2003 10:00 PM
To: Struts Users Mailing List
Subject: Re: [newbie] Connection Pooling
On 2/12/2003 10:34 PM, Marco Tedone wrote:
You could write a PlugIn(new
On 2/12/2003 11:20 PM, Guido wrote:
IMHO, storing the connection in the session context is *never* a good
idea!
1. Session timeout uses to be too high if you must wait the session to
expire to close your connection (the user closes the browser...)
2. You can kill your DB or you app server...
Why wouldn't you use a simple update statement on the revised, validated
data, rather than keeping the connection open for long?
Z.
Folks,
quite new to Struts and it's way to JPS-Action-etc. chaining I'd like to
know the following. Is their a way to keep open a certain connection to
a
12 matches
Mail list logo
