rs Mailing List
Subject: RE: Thread-safety
Hi,
Yes. We use this code from within a controller stored in the user
session. Now each user will get the controller from his session and call
this code from within the controller but even then this might be a bit
tricky. Our controller doesn'
nks,
Mohan
-Original Message-
From: Andrew Hill [mailto:[EMAIL PROTECTED]]
Sent: Friday, November 22, 2002 11:27 AM
To: Struts Users Mailing List
Subject: RE: Thread-safety
It depends...
-Original Message-
From: Mohan Radhakrishnan [mailto:[EMAIL PROTECTED]]
Sent: Friday, November 2
It depends...
-Original Message-
From: Mohan Radhakrishnan [mailto:[EMAIL PROTECTED]]
Sent: Friday, November 22, 2002 13:20
To: Struts Users Mailing List
Subject: Thread-safety
Hi,
getServlet().getServletContext() );
I have code like this in my reload action. Now this gets
Hi,
getServlet().getServletContext() );
I have code like this in my reload action. Now this gets hold of the
application context and refreshes it from the database. Since actions are
reused we think there might be some problem with thread safety.
Does it make sense to use code like
On Wed, 28 Aug 2002, Kevin A. Smith wrote:
> Date: Wed, 28 Aug 2002 14:24:03 -0400
> From: Kevin A. Smith <[EMAIL PROTECTED]>
> Reply-To: Struts Users Mailing List <[EMAIL PROTECTED]>
> To: Struts Users Mailing List <[EMAIL PROTECTED]>
> Subject: RE: JSP thr
Kevin
-Original Message-
From: Galbraith, Paul [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 28, 2002 2:21 PM
To: Struts Users Mailing List
Subject: RE: JSP thread safety
Ok, I think I understand for scriptlets: essentially, any JSP declarative tag is not
thread-safe, but sta
On Wed, 28 Aug 2002, Galbraith, Paul wrote:
> Date: Wed, 28 Aug 2002 13:34:07 -0400
> From: "Galbraith, Paul" <[EMAIL PROTECTED]>
> Reply-To: Struts Users Mailing List <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: JSP thread safety
>
> Can s
it, and then reused within that request if more than one
reference is made?
Paul
-Original Message-
From: James Higginbotham [mailto:[EMAIL PROTECTED]]
Sent: August 28, 2002 2:03 PM
To: Struts Users Mailing List
Subject: RE: JSP thread safety
Well, the JSP spec says it all - may want to
ared within the body of the generated method by the JSP compiler
and thus they go on the stack for the thread, rather than the heap.
James
> -Original Message-
> From: Kevin A. Smith [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, August 28, 2002 12:54 PM
> To: Struts Us
Not sure about the taglib class variables (but I'd really like the answer to that one
also).
With respect to JSP thread safety, my understanding was that any variables declared in
the page were only in scope during the execution of the page, much like variables in
method scope. If the
Can someone clear up basics of JSP thread safety for me? Can I declare variables in
scriptlets and maintain thread safety? Also, what about custom tags. They declare
class variables, which makes me nervous...does the container ensure thread safety for
custom tags (assuming they release
On Thu, Jun 13, 2002 at 09:07:58PM -0700, Craig R. McClanahan wrote:
>
> Not always. Example -- let's say you have a String property (very common
> in a form bean), so you have a setter like:
>
> private String foo = null;
>
> public String getFoo() {
> return (this.foo);
> }
>
>
On Thu, 13 Jun 2002, Noah Levitt wrote:
> Date: Thu, 13 Jun 2002 14:45:35 -0400
> From: Noah Levitt <[EMAIL PROTECTED]>
> Reply-To: Struts Users Mailing List <[EMAIL PROTECTED]>
> To: Struts Users Mailing List <[EMAIL PROTECTED]>
> Subject: Re: thread safety
-
From: Noah Levitt [mailto:[EMAIL PROTECTED]]
Sent: Friday, June 14, 2002 02:46
To: Struts Users Mailing List
Subject: Re: thread safety
Hello,
Your suggestion is duly noted, and would probably be good
advice for many web apps. But keeping form beans in session
scope can be very handy at times
. McClanahan wrote:
>
>
> The simplest way to avoid this whole set of problems is to use request
> scope for your form beans. Then, the container guarantees that only one
> thread can access these beans, so you don't need to be concerned at all
> about thread safety in them.
>
required for the wizard in a DVO and not a form bean. This helps keep
>form beans in request and thus enables thread safety. On each page of the wizard, you
>update the DVO with the values in the form bean and only keep the DVO in session.
> > I agree with Craig when he says that the fo
> In reply to an earlier post regarding something similar, my idea is to encapsulate
>the information required for the wizard in a DVO and not a form bean. This helps keep
>form beans in request and thus enables thread safety. On each page of the wizard, you
>update the DVO with the
Subject: Re: thread safety
From: "srinivas sunkara" <[EMAIL PROTECTED]>
===
Irrespective of the frombean being in the session scope or a DVO being
in a session the threading issues are still the same. The two ways you can
resolve them is to have your form bean or formbean an
uired for the wizard in a DVO and not a form bean. This helps keep form
beans in request and thus enables thread safety. On each page of the wizard, you
update the DVO with the values in the form bean and only keep the DVO in session.
I agree with Craig when he says that the form bean should only b
(ie: wizards etc...)
-Original Message-
From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 13, 2002 14:17
To: Struts Users Mailing List
Subject: Re: thread safety
On Wed, 12 Jun 2002, Noah Levitt wrote:
> Date: Wed, 12 Jun 2002 19:57:39 -0400
> From: Noah
On Wed, 12 Jun 2002, Noah Levitt wrote:
> Date: Wed, 12 Jun 2002 19:57:39 -0400
> From: Noah Levitt <[EMAIL PROTECTED]>
> Reply-To: Struts Users Mailing List <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: thread safety
>
> Hello struts users,
>
>
Hello struts users,
The issue of thread safety bugs me. It seems as though it is
standard practice to write servlets thread-*unsafely*. The
odds of it ever being a problem are slim, but still.
It seems to me that form bean setters (and probably getters)
should be synchronized. I found the
in a method or be a globaly syncronized object for all
to use?
-Original Message-
From: Jeff Martin [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 05, 2002 12:26 PM
To: Struts Users Mailing List
Subject: RE: Thread Safety Question (was Formatting Dates, Integers...)
Any u
.
Jeff
-Original Message-
From: Keith Bacon [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 05, 2002 5:12 AM
To: Struts Users Mailing List
Subject: Thread Safety Question (was Formatting Dates, Integers...)
Do you know what the problem was that made your use of format objects non-thread
Do you know what the problem was that made your use of format objects non-thread safe?
> -Original Message-
> From: Jeff Martin [mailto:[EMAIL PROTECTED]]
> Sent: Monday, February 04, 2002 5:56 PM
> To: Struts Users Mailing List
> Subject: RE: Formatting Dates, Integers...
>
>
> Be very
On Wed, 11 Jul 2001 [EMAIL PROTECTED] wrote:
> Hi all,
> I'm wondering if the struts tags are thread safe?
>
On a propertly implemented container, all custom tags (not just the Struts
ones) are thread safe. The JSP spec requires that a single custom tag
instance be used by only one reque
Hi all,
I'm wondering if the struts tags are thread safe?
I have a view which has two frames, each with a jsp page using the
logic:iterate referencing the same collection. When I request the page
which defines the frames and thus loads both jsp pages at the same time
I get exceptions thro
ot the only one who finds your
attitude offensive.
-Original Message-
From: Jonathan
Sent: Thu 4/26/2001 1:47 PM
To: [EMAIL PROTECTED]; Ryan Rich
Cc:
Subject: Re: FormBeans and Thread Safety
Where in the docs does it say that Action objects are pooled?!!
- Ori
Where in the docs does it say that Action objects are pooled?!!
- Original Message -
From: "Rajan Gupta" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>; "Ryan Rich" <[EMAIL PROTECTED]>
Sent: Thursday, April 26, 2001 8:58 AM
Subject: Re: FormBeans an
No. ActionForm are created for each request, While Action need to
threadsafe, because Action's are pooled
--- Ryan Rich <[EMAIL PROTECTED]> wrote:
> When creating a FormBean (a class extending ActionForm), do they need to
> be
> thread-safe?
>
> Ryan Rich
>
> Bitek
When creating a FormBean (a class extending ActionForm), do they need to be
thread-safe?
Ryan Rich
Bitek, Inc.
2569 West Woodland Dr.
Anaheim, CA 92801
(714) 828-8388
have referred to using the token methods of Action to detect
> duplicate requests (from the user clicking more than once without waiting
> for a new page). For an example, see
> http://www.mail-archive.com/struts-user@jakarta.apache.org/msg02368.html.
>
> Are there thread safety issue
Previous posts have referred to using the token methods of Action to detect
duplicate requests (from the user clicking more than once without waiting
for a new page). For an example, see
http://www.mail-archive.com/struts-user@jakarta.apache.org/msg02368.html.
Are there thread safety issues
Greg Reddin wrote:
> I have some issues with thread safety and could use some advice. Please look at
> my assumptions and tell me if they are true or not.
>
> 1) Tomcat (or other container) creates one instance of the ActionServlet,
> ActionBase, and all my Action classes and
I have some issues with thread safety and could use some advice. Please look at
my assumptions and tell me if they are true or not.
1) Tomcat (or other container) creates one instance of the ActionServlet,
ActionBase, and all my Action classes and caches them for performance reasons
35 matches
Mail list logo
