1 of 1 people found this helpful
I don't think "querying" the journal directly is feasible. Why not use a message selector? The JMS message selector's syntax is based on a subset of the SQL92 conditional expression syntax.
A selector will not help, because I want to get messages with timestamp later than a given one. And this given one will vary between queries and clients.
Moreover, my clients will not use JMS directly. They will connect to a webapp that will return only the selected messages given the filter.
So what I will finally do is create a MDB that will consume messages later and put them in database.
We have the PrintData tool, and Justin is working on an export Tool to export messages on a XML format.
You can create a Consumer with the filter you want maybe? You can't query the journal like a database after a message system is not a database.
(that approach usually fails really badly with any message system you choose)
I'm still not sure why a selector wouldn't work. You can query on JMSTimestamp.
Also, your clients don't necessarily need to use JMS directly. If they are connecting to a webapp then the webapp can use a JMS selector and then return the results to the client in whatever format is appropriate.