[jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1681) fetch based on messageId doesn't work

[ https://jira.jboss.org/jira/browse/JBMESSAGING-1681?page=com.atlassian.ji... ] Konstantin Pupkov commented on JBMESSAGING-1681: ------------------------------------------------ You didn't get my complain. I tried JMSMessageID as well - it doesn't work. It works fine with JBOSS 4.1.GA. I tried to find workaround that is why I tried "JBMessageID" in my sample. here is link to JBMessageID: JavaDoc class: org.jboss.messaging.core.filter.impl.FilterImpl public class FilterImpl extends java.lang.Object implements Filter This class implements a JBoss Messaging filter Version: $Revision: 3569 $ $Id: Selector.java 3569 2008-01-15 21:14:04Z timfox $ Author: Tim Fox, Jeff Mesnil JBM filters have the same syntax as JMS 1.1 selectors, but the identifiers are different. Valid identifiers that can be used are: *******!!!!!!!JBMessageID!!!!!!!!******** - the message id of the message JBMPriority - the priority of the message JBMTimestamp - the timestamp of the message JBMDurable - "DURABLE" or "NON_DURABLE" JBMExpiration - the expiration of the message JBMSize - the encoded size of the full message in bytes Any other identifers that appear in a filter expression represent header values for the message String values must be set as SimpleString, not java.lang.String (see JBMESSAGING-1307). Derived from JBoss MQ version by, Norbert Lataille, Juha Lindfors, Jason Dillon, Scott Stark, Tim Fox -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira