Yup - your issue is still valid as disabling message ids doesn't appear to be working.
> -----Original Message----- > From: Teemu Torma [mailto:[EMAIL PROTECTED] > Sent: Wednesday, March 14, 2007 9:39 AM > To: [email protected] > Subject: Re: Suggested change to CMS for Message IDs > > On Wednesday 14 March 2007 14:03, Mittler, Nathan wrote: > > I noticed in the .NET client, there is only a getter for > NMSMessageId, > > and no setter. While it deviates from the JMS API, I think > this makes > > it a bit more clear and would like to remove the > setCMSMessageId from > > the CMS API. > > > > Any objections to doing this? > > No objection from me. I just filed the item because the > method was there and did not work (and it did work for stomp). > > Teemu >
