qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John O'Hara" <john.r.oh...@gmail.com>
Subject Re: Can somebody explain the logic behind the criteria to make a message read-only
Date Sat, 02 Dec 2006 23:29:54 GMT
Which tests, Java TCK, or Qpid tests?

Some messaging systems do treat messages as immutable once sent and you may
not be able to change a message you receive.

I'm not sure if we've figured that one through yet..  this has repurcussions
for the AMQP spec and portable messaging.

John

On 02/12/06, Rajith Attapattu <rajith77@gmail.com> wrote:
>
> Hi Folks,
>
> Some tests are failing as it throws MessageNotWriteableException when
> trying
> to add properties.
> This exception is throw when _readableProperties is set to true in the
> AbstractJMSMessage.
>
> After some close inspection I see the following logic in the
> AbstractJMSMessage constructors
>
>         _readableProperties = (_contentHeaderProperties != null);
>         _readableMessage = data != null;
>
> Why is this done this way ?
>
> As a temorary messure I just set the above to properties to false and now
> it
> results in more tests being passed.
> However I would like to understand the reason behind the above logic to
> provide a proper fix.
>
> Comments are appreciated.
>
> Regards,
>
> Rajith
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message