The way they behave now, is correct per the JMS spec. Adding that flag would be a way to alter the behaviour defined be the JMS spec.
The spec states that a durable subscriber will only receive messages that were published AFTER his subscription is initially created. On 4/10/06, ErinO <[EMAIL PROTECTED]> wrote: > > Hi, James: > > Thanks for the explanation. The configuration flag will do for my case. > > But I thought the purpose for the durable topic is to remove the order > dependency between the producer and the consumer. Also for a message to be > durable means it shouldn't get lost in any circumstances, if someone didn't > turn on the configuration flag you are going to add, he could lose messages > in this specific case. > > In my opinion, it is better to fix the issue than just adding a > configuration flag. > > Thanks. > > Erin > -- > View this message in context: > http://www.nabble.com/ActiveMQ-4.0-RC1---durable-topic-t1426256.html#a3846446 > Sent from the ActiveMQ - Dev forum at Nabble.com. > > -- Regards, Hiram
