qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rob Godfrey (JIRA)" <qpid-...@incubator.apache.org>
Subject [jira] Closed: (QPID-160) Implement ConnectionMetaData to do optional JMS Defined Properties
Date Wed, 12 Dec 2007 11:31:43 GMT

     [ https://issues.apache.org/jira/browse/QPID-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Rob Godfrey closed QPID-160.

       Resolution: Won't Fix
    Fix Version/s:     (was: M3)

Will implement other properties only if get specific user requirements

> Implement ConnectionMetaData  to do optional JMS Defined Properties
> -------------------------------------------------------------------
>                 Key: QPID-160
>                 URL: https://issues.apache.org/jira/browse/QPID-160
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Java Client
>            Reporter: Martin Ritchie
>            Priority: Minor
> Some values are part of the AMQMessage header but they need to be exposed via 
> AMQConnection - ConnectionMetaData getMetaData()
>  currently returns null
> From the JMS Spec
> 3.5.9 JMS Defined Properties
> JMS reserves the 'JMSX' property name prefix for JMS defined properties. The
> full set of these properties is provided in Table 3-3. New JMS defined
> properties may be added in later versions of JMS.
> Unless noted otherwise, support for these properties is optional. The
> Enumeration ConnectionMetaData.getJMSXPropertyNames() method returns the
> names of the JMSX properties supported by a connection.
> JMSX properties may be referenced in message selectors whether or not they
> are supported by a connection. If they are not present in a message, they are
> treated like any other absent property.
> The existence, in a particular message, of JMS defined properties that are set by
> a JMS provider depends on how a particular provider controls use of the
> Properties are:
> JMSXUserID String
> JMSXAppID String
> JMSXDeliveryCount int
> JMSXGroupID String
> JMSXGroupSeq int
> JMSXProducerTXID String
> JMSXConsumerTXID String
> JMSXRcvTimestamp long
> JMSXState int
> JMSX properties set by the provider on send are available to both the producer
> and the consumers of the message. JSMX properties set by the provider on
> receive are available only to the consumers.
> JMSXGroupID and JMSXGroupSeq are standard properties clients should use if
> they want to group messages. All providers must support them.
> The case of these JMSX property names must be as defined in the table above.
> Unless specifically noted, the values and semantics of the JMSX properties are
> undefined.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message