[ http://issues.apache.org/jira/browse/QPID-160?page=comments#action_12457391 ] Rajith Attapattu commented on QPID-160: ---------------------------------------
Martin, I have added an implementation of this class in rev 485735. However I haven't added the JMSX properties, I would appreciate if you can add those to the class. I just only implemented the bare minimum to pass the TCK. Regards, Rajith > Implement ConnectionMetaData to do optional JMS Defined Properties > ------------------------------------------------------------------- > > Key: QPID-160 > URL: http://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. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
