That fixed our problem that has been nagging us for little over a week. If
only, I had posted this earlier to the group :-)
Thanks a bunch
>>> [EMAIL PROTECTED] 07/22/05 4:17 PM >>>
Srinivas Gunturu wrote:
>Most of our action classes are extended from a BaseAction class which
>initializes pro
Srinivas Gunturu wrote:
Most of our action classes are extended from a BaseAction class which
initializes protected variables such as session, user bean, ActionForm, request
and response objects inside an init method which is called by decendents in the
execute method.
Sounds like instance v
Srinivas Gunturu wrote:
Most of our action classes are extended from a BaseAction class which
initializes protected variables such as session, user bean, ActionForm, request
and response objects inside an init method which is called by decendents in the
execute method.
Sounds like instance v
Most of our action classes are extended from a BaseAction class which
initializes protected variables such as session, user bean, ActionForm, request
and response objects inside an init method which is called by decendents in the
execute method.
Sounds like instance variables inside an action c
Srinivas Gunturu wrote:
We don't have any static method calls or static objects we reference in action
classes.
Do you have any _instance_ variables in any servlets, actions, filters,
etc.?
I will almost guarantee you that you are accessing a non-synchronized
object or instance data.
D
5 matches
Mail list logo
