Thank you very much for quick fix!
I'll do with it again after released.
On Wed, 16 May 2001 15:29:07 +0200
"Andreas Mueller" <[EMAIL PROTECTED]> wrote:
> Well, we found it. When using an ObjectMessage which was received before,
> the internal state is not resetted on setObject()/clearBody(). So when
> sending, SwiftMQ assumes that the content is already a byte stream which
> leads to a ClassCastException. Workaround is to use a new message for the
> reply.
>
> This bug has been fixed for release 2.1.0 which will be offered on
> Friday, 18th May. 2.1.0 contains fixes of all known bugs, some
> enhancements, changes & improvements.
kats
------------------------------------------------------
SwiftMQ developers mailing list * http://www.swiftmq.com
To unsubscribe from this list, send an eMail to
[EMAIL PROTECTED] and write in the body of your message:
UNSUBSCRIBE developers <your-email-address>
Archive: http://www.mail-archive.com/developers@mail.iit.de/
