summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGordon Sim <gsim@apache.org>2012-05-01 15:00:17 +0000
committerGordon Sim <gsim@apache.org>2012-05-01 15:00:17 +0000
commitc4ea1753628be4013e2d26767f03fe21b9a7e1e7 (patch)
tree256d075551e21d2d7770dc7fb6e07c17dd69e238
parent149204126179b0129ddd9ad643c57bc4958bef59 (diff)
downloadqpid-python-c4ea1753628be4013e2d26767f03fe21b9a7e1e7.tar.gz
Clarified that syntax for selector filter is based on the selector syntax in the JMS specification
git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk@1332680 13f79535-47bb-0310-9956-ffa450edef68
-rw-r--r--qpid/specs/apache-filters.xml10
1 files changed, 7 insertions, 3 deletions
diff --git a/qpid/specs/apache-filters.xml b/qpid/specs/apache-filters.xml
index f3bebc14ad..24e1d521e2 100644
--- a/qpid/specs/apache-filters.xml
+++ b/qpid/specs/apache-filters.xml
@@ -147,9 +147,13 @@
<descriptor name="apache.org:selector-filter:string" code="0x0000468C:0x00000004"/>
<doc>
<p>
- The Java Message Service "selector" defines an SQL like syntax for filtering messages.
- The selector filters based on the values of "headers" and "properties". The defined
- JMS headers can be mapped to equivalent fields within the AMQP message sections:
+ The Java Message Service "selector" defines an SQL like
+ syntax for filtering messages. The selector filters based
+ on the values of "headers" and "properties". The
+ selector-filter uses the selector as defined by JMS but
+ with the names of JMS headers translated into their AMQP
+ equivalents. The defined JMS headers can be mapped to
+ equivalent fields within the AMQP message sections:
</p>
<picture title="Mapping JMS Headers to AMQP fields">
JMS Header Name | AMQP 1.0 Field