Re: [jira] Updated: (QPID-1766) Implemention of selector using Xquery

2009-03-22 Thread chenta lee
I already add an option to let user decide whether parse the content or not. setting.arguments.setInt("qpid.selector_parse_content", 1); set qpid.selector_parse_content to 1 will enable broker to parse the message content, vice versa. Chenta On Mon, Mar 23, 2009 at 10:10 AM, Carl Trieloff wrote:

Re: [jira] Updated: (QPID-1766) Implemention of selector using Xquery

2009-03-22 Thread Carl Trieloff
Robert Greig wrote: 2009/3/22 chenta lee : Yes, what I mean is the concept of message selector, not how we implement it. And Xquery is mush more powerful than SQL-92 syntax.By MQ, I refer to Message Queue instead of a particular message queue project. OK. xquery may be semantically ri

[jira] Commented: (QPID-1511) JMX Interface does not require authentication

2009-03-22 Thread Robert Gemmell (JIRA)
[ https://issues.apache.org/jira/browse/QPID-1511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12688179#action_12688179 ] Robert Gemmell commented on QPID-1511: -- Added scripts to generate example ssl stores in

[jira] Assigned: (QPID-1767) messageAge units are not listed in MangedQueue

2009-03-22 Thread Robert Gemmell (JIRA)
[ https://issues.apache.org/jira/browse/QPID-1767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Gemmell reassigned QPID-1767: Assignee: Aidan Skinner (was: Robert Gemmell) Hi Aidan, can you review this change please,

[jira] Updated: (QPID-1767) messageAge units are not listed in MangedQueue

2009-03-22 Thread Robert Gemmell (JIRA)
[ https://issues.apache.org/jira/browse/QPID-1767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Gemmell updated QPID-1767: - Status: Ready To Review (was: In Progress) > messageAge units are not listed in MangedQueue > ---

[jira] Created: (QPID-1767) messageAge units are not listed in MangedQueue

2009-03-22 Thread Robert Gemmell (JIRA)
messageAge units are not listed in MangedQueue -- Key: QPID-1767 URL: https://issues.apache.org/jira/browse/QPID-1767 Project: Qpid Issue Type: Bug Components: Java Broker Affects Ver

Re: [jira] Updated: (QPID-1766) Implemention of selector using Xquery

2009-03-22 Thread Robert Greig
2009/3/22 chenta lee : > Yes, what I mean is the concept of message selector, not how we implement > it. And Xquery is mush more powerful than SQL-92 syntax.By MQ, I refer to > Message Queue instead of a particular message queue project. OK. xquery may be semantically richer but the JMS message s

Re: [jira] Updated: (QPID-1766) Implemention of selector using Xquery

2009-03-22 Thread chenta lee
Yes, what I mean is the concept of message selector, not how we implement it. And Xquery is mush more powerful than SQL-92 syntax.By MQ, I refer to Message Queue instead of a particular message queue project. I am a little confused about how could my patches related to patent issue? Chenta On Su

Re: [jira] Updated: (QPID-1766) Implemention of selector using Xquery

2009-03-22 Thread Robert Greig
2009/3/22 chenta lee : > Message selector is a popular and essential feature for MQ(ActiveMQ already > implemented it). I am not sure if they can patent it. Can you be a bit more explicit about what you mean? Are you referring the JMS selectors but with semantics that enable the use of xquery on

Re: [jira] Updated: (QPID-1766) Implemention of selector using Xquery

2009-03-22 Thread chenta lee
Message selector is a popular and essential feature for MQ(ActiveMQ already implemented it). I am not sure if they can patent it. Chenta On Sun, Mar 22, 2009 at 4:18 AM, James Mansion wrote: > chenta lee (JIRA) wrote: > >> [ >> https://issues.apache.org/jira/browse/QPID-1766?page=com.atlassi