Actually it's worse than that. If you change the default parser to SelectorParser, nothing works! So a simple slector like type='cadex' bombs.
Jason Dillon wrote: > I did not think we were using the old parser anymore... Is there a > reason this is still around after Scott reimplemented in JavaCC? > > --jason > > > On Wed, 2002-02-13 at 16:53, Dave Smith wrote: > >>After having a bad day trying to get a message selector working for a >>topic listener I came across a few bugs. >> >>1) If the message selector is invalid but the connection is not started >>but no error is thrown. So if you createTopicSession then >>createSubscriber and then start the connection the connection looks good >>but there are no messages delivered. (I spent most of the day trying to >>sort this one out) >> >>2) The message selectors do not seem to like boolean types. My query is >>app_id='AK' and production=TRUE >> >>3) What parser are we using for the message selectors. I thought we were >>using javacc and jms.jj. But in Selector the default is set to parser >>which is from jms.y. I don't even think this thing is getting >>re-processed. I did swicth the default to SelectorParser but that did >>not work as well. >> >> >>_______________________________________________ >>Jboss-development mailing list >>[EMAIL PROTECTED] >>https://lists.sourceforge.net/lists/listinfo/jboss-development >> > > _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development