activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "james strachan (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AMQ-340) allow topics in particular but also queues to have a 'namespace URI' like WS-Notification
Date Mon, 03 Jul 2006 10:57:51 GMT
    [ https://issues.apache.org/activemq/browse/AMQ-340?page=comments#action_36503 ] 

james strachan commented on AMQ-340:
------------------------------------

Its been a while - I've kinda forgotten :)

I think the idea was to allow different 'roots'. By default in JMS there is one global topic
namespace where > will receive every message. In WS-Notification you can have many 'root's.
e.g. its a bit like having a topic which is owned by a particular broker.

So I guess its more about having optional 'owners' of the topic namespace - so it could be
a global foo.bar or could be foo.bar within the 'cheese' domain which might be owned by a
particular broker

> allow topics in particular but also queues to have a 'namespace URI' like WS-Notification
> -----------------------------------------------------------------------------------------
>
>          Key: AMQ-340
>          URL: https://issues.apache.org/activemq/browse/AMQ-340
>      Project: ActiveMQ
>         Type: New Feature

>     Reporter: james strachan
>      Fix For: 4.1

>
>
> This would allow a real clean mapping from WS-N topics and ActiveMQ at the protocol level.
We could use the namespace as a level of indirection to map to a broker, a cluster of brokers
or even a particular area of a network etc. The namespace could be a broker's name too.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message