|
From: Leonardo K. S. <sh...@gm...> - 2006-02-07 11:49:43
|
Just try to implement a durable subscription using selectors as showed in http://www.devx.com/Java/Article/21261/, which says >>>>>>>> (...) You can also filter using message priority. For example, you can change the filter query to: String filterQuery =3D "JMSPriority > 6"; topicSubscriber =3D topicSession.createSubscriber(topic, filterQuery, false); Now when you run the client application, Figure 3 shows that the application consumes only messages with a JMSPriority higher than 6. Everything else was filtered. (...) >>>>>>>> which seems not to be true, because all messages are consumed and removed from the openjms.messages table another guy asked the same thing in october and get no answers http://thread.gmane.org/gmane.comp.java.openjms.user/1384 is it an openjms bug? or am I getting something wrong? what I would really like is some kind of topic where I could publish messages to several consumers that will consume selectively, using JMS selectors, and leaving the other messages there for the other consumers. Is it possible using JMS? regards Kenji _______________________ http://kenjiria.blogspot.com http://gaitabh.blogspot.com |