Yes, this is expected behavior. The NMS API maps to the JMS API. It is not an exact implementation of JMS. It is it's own thing that has the same functionality as the JMS API.
On Mon, Aug 17, 2015, 3:55 PM fmansoor <faisal.mans...@gmail.com> wrote: > Hi everyone, > > I am trying to understand how the .Net Apache.NMS.ActiveMQ client handles > standard JMS properties. Message group is properly set when I use > "NMSXGroupID" property but not with "JMSXGroupID". Is this expected? > Shouldn't .Net client support the standard JMS header strings? > > Thanks. > Faisal > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/ActiveMQ-Net-Difference-between-NMSXGroupID-and-JMSXGroupID-tp4701166.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
