activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nathan Mittler (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AMQCPP-124) Provide a ConnectionMetaData interface in CMS
Date Sat, 04 Aug 2007 21:06:49 GMT

    [ https://issues.apache.org/activemq/browse/AMQCPP-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39841
] 

Nathan Mittler commented on AMQCPP-124:
---------------------------------------

Ah - I was referring to Provider Major and Minor versions - you're referring to JMS Major
and Minor versions.  

I would say we can leave out the CMS Major and Minor versions altogether ... doesn't really
add any benefit.  Rather, we could just stick with provider version information to get info
about the particular connector.

> 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.


Mime
View raw message