[
https://issues.apache.org/activemq/browse/AMQCPP-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39839
]
Nathan Mittler commented on AMQCPP-124:
---------------------------------------
I'm not sure that the Major and Minor versions should come from the client
build versions. I was thinking they would just be protocol-specific version
info. For example, if a connection is using openwire v2, the major version
would be 2. So basically, the connector would hard-code the version info for
whatever it supports. Does this make sense?
> Provide a ConnectionMetaData interface in CMS
> ---------------------------------------------
>
> Key: AMQCPP-124
> URL: https://issues.apache.org/activemq/browse/AMQCPP-124
> Project: ActiveMQ C++ Client
> Issue Type: Improvement
> Components: CMS Impl
> Affects Versions: 2.1
> Reporter: Albert Strasheim
> Assignee: Timothy Bish
> Priority: Trivial
> Fix For: 2.2
>
>
> From the JMS 1.1 specification:
> 4.3.7 ConnectionMetaData
> A Connection provides a ConnectionMetaData object. This object provides the
> latest version of JMS supported by the provider as well as the provider's
> product name and version.
> It also provides a list of the JMS defined property names supported by the
> connection.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
