2008/8/27 Jim Gomes <[EMAIL PROTECTED]>: > Hi James, > > There was an implementation gap on this area. I refactored this area of the > code. Feel free to look over it to make sure I did things right. I wanted > to make the IMessage.Properties transparent to use and interchangeable with > the SetObjectProperty/GetObjectProperty functions.
Ah cool! Maybe its not working then? :) > A user should now be able to set the extended properties on ActiveMQMessage > from the IMessage.Properties interface by matching the property names. > > I am surprised that the NMSXGroupID is not part of the main IMessage > interface, as I think it is part of the JMS spec (JMSXGroupID), isn't it? Yeah - maybe we could move NMSXGroupID to the IMessage interface? Given the NMSX prefix its marked as an optional header a provider may support etc -- James ------- http://macstrac.blogspot.com/ Open Source Integration http://open.iona.com
