Awesome stuff BTW Ian - I'd *love* a J2ME Stomp/ActiveMQ client :) BTW the correlation-id is the Stomp-approved name for passing along the correlationID; in JMS-land its really a property called JMSCorrelationID, so changing your selector header to
activemq.selector:JMSCorrelationID= '11143353544334-0' Should do the trick I think. I confess this renaming of JMSCorrelationID -> correlation-id in Stomp could be a bit confusing for folks; maybe it'd be better if we let folks keep the regular JMS* style headers? (It'd be easy to support both BTW) James Ian de Beer wrote: > > Hi > I have developed a J2ME client for ActiveMQ using the Stomp protocol. > I would be happy to contribute this to the project, but I have a real > show stopper issue that I cannot seem to resolve. > I use it in a request/response mode with the request and > subscription looking like this: > SEND > destination:/queue/Mobile.Queue > reply-to:/queue/Temp.Queue > correlation-id:11143353544334-0 > > <?xml version='1.0' encoding='UTF8' ?><request><id>loginValidation</ > id><bean>eFileHandler</bean><method>loginValidation</ > method><params><password>abc</password><username>ian</username></ > params></request> > > ^@ > > and : > > SUBSCRIBE > destination:/queue/Temp.Queue > activemq.selector:correlation-id = '11143353544334-0' > ack:client > > ^@ > > Despite various permutations of correlation-id and selector settings, > the clients keep consuming each others messages. Could someone please > tell me what the Stomp syntax is for selecting messages with a > specific correlation-id from the queue. > > Regards > Ian > > -- View this message in context: http://www.nabble.com/ActiveMQ-client-for-J2ME-t1354154.html#a3627782 Sent from the ActiveMQ - Dev forum at Nabble.com.
