On 13/07/2012 10:39, Nick Wright wrote:
>
> Regarding the metadata API on JIRA (http://java.net/jira/browse/JMS_SPEC-59), as we move towards cloud/PaaS
>
> environments in JEE7 I think a more standardised API for viewing and managing subscriptions certainly becomes a lot
>
> more important. Certainly there are a number of times I have found it greatly beneficial to monitor and purge complex,
> clustered messaging systems in test and production environments to clear unexpected system states. Were something like
> this made available I would like to see the ability to centrally view cluster subscriptions regardless of the attach
> point of a consumer; given
>
> that implementations must maintain some sort of routing table for producer message input I expect that something of
> this nature would be available on all JMS cluster nodes.
>
> Unfortunately I think there are some more pressing standardisations (hence my votes!), so perhaps the API is a good
> candidate for JMS 2.1?
If and when we get to consider the content for JMS 2.1 then I'll make sure this
(
http://java.net/jira/browse/JMS_SPEC-59) gets considered.
Nigel