That makes sense. Thanks for the help...
dave
-Original Message-
From: Cakalic, James P. [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, November 21, 2001 3:03 PM
To: 'Struts Users Mailing List'
Subject: RE: Member variables in Actions
Quoting from the Struts User'
Quoting from the Struts User's Guide:
"The controller servlet creates only one instance of your Action class, and
uses it for all requests. Thus, you need to code your Action class so that
it operates correctly in a multi-threaded environment, just as you must code
a servlet's service method safe
e. If there would be a problem then synchronize the methods or blocks of
code that manipulate/use the instance variables.
Hal
-Original Message-
From: John Hunt
To: [EMAIL PROTECTED]
Sent: 2/4/01 4:21 AM
Subject: Re: member variables
What about anything that is put in the session
object???
What about anything that is put in the session
object??? When should I worry about synchronization
about such objects?
Suppose I put an object which has some some methods in
it? When should I worry about synchronization in the
code that lies in it?
Suppose I put an object in session and open two
b
This reminds me of another question I've been meaning to ask.
Once upon a time, in a discussion of Business Logic Beanies, I
mentioned a "QueryFormBean", which is basically a poor man's uncached
RowSet. This is mean to encapsulate the JDBC red-tape, along with the
SQL command, the latter being r
Ted Husted wrote:
> There is a single action object per session.
Um, actually it is per *application*, not per *session*. All users who call
the same action URI are sharing the same action instance.
The primary implication of this is that instance variables in your action
classes are shared ac
truts List
Subject: Re: member variables
There is a single action object per session. You do need to take care
of any concurrency issues. The use of instance variables where possible
is recommended.
See <
http://jakarta.apache.org/struts/userGuide/building_controller.html#acti
on_class
There is a single action object per session. You do need to take care
of any concurrency issues. The use of instance variables where possible
is recommended.
See <
http://jakarta.apache.org/struts/userGuide/building_controller.html#acti
on_classes > for more, starting with "Design issues to reme
8 matches
Mail list logo