If you create patches you can attach them to this issue:
https://issues.apache.org/activemq/browse/AMQCPP-172
You can compare the current version of ActiveMQMapMessage to the
previous one in SVN to find the changes.
Version 2.2 is not yet released.
To save you some time, here is the basic fix change copyDataStructure to
look like this. Note that this was only a bug when using the async
transport.
virtual void copyDataStructure( const DataStructure* src ) {
ActiveMQMessageBase<cms::MapMessage>::copyDataStructure( src );
const ActiveMQMapMessage* srcMap =
dynamic_cast< const ActiveMQMapMessage* >( src );
if( srcMap != NULL && srcMap->map != NULL ) {
this->map = new util::PrimitiveMap( *srcMap->map );
}
}
On Mon, 2008-03-10 at 00:40 -0700, stevenbohrer wrote:
> Hi Tim,
>
> I've implemented the Map and List types now, and will work on submitting
> them with the proper tests, etc. However, I have another issue, I'm using a
> Topic with MapMessages, and they don't seem to be received properly. I
> found https://issues.apache.org/activemq/browse/AMQCPP-166 which seems to
> describe the same problem, and notes it was resolved in V2.2. Is that
> version available yet? If not (and I hope this isn't too much of a pain),
> can you send me the fix, or tell me how to resolve the issue?
>
> Thanks,
>
> Steve
>
>
