cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jorg Heymans <>
Subject RE: thread safety of cocoon
Date Mon, 01 Sep 2003 14:18:53 GMT
When you say a new component then you mean new class right?
I don't want the class it to be accessed by more than 1 thread at the same
time, are you saying this is the default behaviour?


-----Original Message-----
From: Upayavira [] 
Sent: Montag, 1. September 2003 15:43
Subject: Re: thread safety of cocoon

Jorg Heymans wrote:

>Say i write my own transformer (or serializer, or generator doesn't
>is it true then that a new instance of my custom class is created each time
>it is executed in a pipeline? (uncached)
>My code relies on a few instance variables (simple ones like Logger but
>more crucial ones like StringBuffers for SAX parsing ), I'ld really hate to
>find out now that instance variables aren't thread safe in cocoon. 
AFAIU, you need to make your component implement ThreadSafe for it to be 
shared across threads. The default is that a new component is created 
for each invocation.

Regards, Upayavira

To unsubscribe, e-mail:
For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message