it is
> like
> this case.
>
> Cheers,
>
> Albert
>
> - Original Message -
> From: "Motl" <[EMAIL PROTECTED]>
> To:
> Sent: Friday, September 21, 2007 1:45 PM
> Subject: Re: BytesMessage constness
>
>
> > Done.
> >
> > https:
September 21, 2007 1:45 PM
Subject: Re: BytesMessage constness
Done.
https://issues.apache.org/activemq/browse/AMQCPP-143
nmittler wrote:
I agree, this definitely would be a pain since the onMessage method gives
you a const Message. Could you capture this issue in JIRA?
http://issues.apache.
nst.
>>
>> I am requesting for that because at the moment such non-const API forces
>> app
>> level either always deal with non-const objects or make
>> const_cast(), that's not good.
>>
>> --
>> View this message in context:
>&
;:
>
> mutable io::ByteArrayInputStream inputStream;
>
> In that case we could keep read methods const.
>
> I am requesting for that because at the moment such non-const API forces
> app
> level either always deal with non-const objects or make
> const_cast(), that's no
ge in context:
http://www.nabble.com/BytesMessage-constness-tf4492790s2354.html#a12813490
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
