On Thu, Mar 18, 2010 at 9:55 AM, jumbro <jum...@fortress.com> wrote:
>
> Thanks for your reply.
>
> I tested your suggestion and it works. I see now that it's the producer that
> determines the persistence.
>
> Do you know off hand how to configure this same behavior using Spring? I'm
> using the NmsTemplate and allowing Spring to manage the underlying messaging
> context. I'm setting NmsTemplate.Persistent = true. I expected that to do
> it, but no dice.
>
> I also tested setting NMSPersistent = true like this:
>
> ...
> template.ConvertAndSendWithDelegate(requestMessage, delegate(IMessage
> message)
> {
> message.NMSPersistent = true;
> return message;
> });
>
> but that didn't do it either.
>
> I'm going to look into it further now, but if you have the answer that would
> be outstanding.
I would think that the persistent property should do it. But given
that's not what you're seeing, I'm at a loss since I've never written
any .NET code. We need the opinion of someone who is familiar with the
.NET client for ActiveMQ and Spring .NET.
Bruce
--
perl -e 'print
unpack("u30","D0G)u8...@4vyy9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
);'
ActiveMQ in Action: http://bit.ly/2je6cQ
Blog: http://bruceblog.org/
Twitter: http://twitter.com/brucesnyder
