"Durable subscribers is an option that we would need so that subscribers don't loose any messages. It's different (though complementary) to the fact that the subscription itself is persisted. For storing the informations needed for subscrition / registration, i think we could leverage the simple JDBC support we have in ServiceMix (see http://svn.apache.org/repos/asf/servicemix/utils/trunk/src/main/java/org/apache/servicemix/jdbc/)."
Can you give me an example of component / code where this is used ? " This can be done independantly from the JMS durable subscription. For the JMS part, I think we should support it in the form of a WS-Notification policy that would be included in the subscription request. For more infos, check the WS-BaseNotification spec, line 622 (which documents the /wsnt:Subscribe/wsnt:SubscriptionPolicy element)" You mean the subscriber will send in his subscription request an element telling that he wants a durable subscription like this (for example) : <wsnt:Subscribe> <wsnt:ConsumerReference> ... </wsnt:ConsumerReference> <wsnt:Filter> ... </wsnt:Filter> <wsnt:SubscriptionPolicy> <wsnt:UseDurable/> </wsnt:SubscriptionPolicy> </wsnt:Subscribe> "It seems there are two different things / options here. The first one would be to check the existence of the underlying JMS topic, but it may make more sense to check only topics that the WS-NotificationBroker knows about (i.e. those that have been advertised through a publisher registration), as we'd need the list to be available for the next point too." Yes, that's it. But if we can retrieve this list, you agree this behaviour can be added to the component ? This would be the default behaviour or would it be specify by a property of the component or a part of the registration / subscription request ? "As for the automatic creation of the topic, there is no JMS compliant way to force the topic creation though it can be done in an activemq specific way." Even if we force the sending of a first notification ? -- View this message in context: http://www.nabble.com/WS-Notification-Component-Improvment-tp19254179p19285408.html Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
