r 16, 2004
5:27 PMTo: [EMAIL PROTECTED]Subject: RE:
Serializer- and Deserializer-objects
multi-threaded?Well, there is
a valueComplete() method that you could override. In the body of the method,
call super.valueComplete() and then "release" your deserializer back int
here...
-Original Message-From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Sent: Thursday, December 16, 2004
5:27 PMTo: [EMAIL PROTECTED]Subject: RE:
Serializer- and Deserializer-objects
multi-threaded?Well, there is
a valueComplete() method that you could override. In the bo
gt; -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, December 14, 2004 1:55 PM
> To: [EMAIL PROTECTED]
> Subject: RE: Serializer- and Deserializer-objects multi-threaded?
>
> The deserializer factory creates the deserializer. Yo
y).
Best
regards and thanks for your hints and ideas,
Mattin
-Original Message-From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday,
December 14, 2004 1:55 PMTo:
[EMAIL PROTECTED]Subject: RE: Serializer- and
Deserializer-objects multi-threaded?
The
deserializer factory c
ecember 14, 2004 12:26 PM
To: [EMAIL PROTECTED]
Subject: Re: Serializer- and Deserializer-objects
multi-threaded?
I've never seen any reference to
threads in descriptions of serializers and deserializers (Axis 1.1).
Certainly, the BeanSerializer has no special code for handling m
(
>
> Best regards from sunny Black Forrest, Germany,
> Mattin
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, December 14, 2004 12:26 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Serializer- and Deserializer-objects m
EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday,
December 14, 2004 12:26 PMTo:
[EMAIL PROTECTED]Subject: Re: Serializer- and
Deserializer-objects multi-threaded?
I've never seen any reference to
threads in descriptions of serializers and deserializers (Axis 1.1).
Certainly, the B
I think they are inherently thread-safe because Axis gets a new instance
each time from your factories. However, some people take short cuts by
making their Serializer/Deserializer classes idempotent and have the
same instances are returned from the factory each time -- which is fine
as long a
I've never seen any reference to threads
in descriptions of serializers and deserializers (Axis 1.1). Certainly,
the BeanSerializer has no special code for handling multiple threads, that
I can see. It looks as though a new serializer/deserializer is created,
from the factory, each time a type nee
