activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dejan Bosanac (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (AMQ-3204) Support non-standard destination path separators
Date Mon, 07 Mar 2011 13:08:59 GMT

     [ https://issues.apache.org/jira/browse/AMQ-3204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Dejan Bosanac resolved AMQ-3204.
--------------------------------

    Resolution: Fixed
      Assignee: Dejan Bosanac

Implemented with svn revision 1078766.

More docs to come.

> Support non-standard destination path separators
> ------------------------------------------------
>
>                 Key: AMQ-3204
>                 URL: https://issues.apache.org/jira/browse/AMQ-3204
>             Project: ActiveMQ
>          Issue Type: New Feature
>    Affects Versions: 5.4.2
>            Reporter: Dejan Bosanac
>            Assignee: Dejan Bosanac
>             Fix For: 5.5.0
>
>
> Wildcards only work on destination paths, separated by standard separator (.), so 
> FOO.>
> FOO.*.BAR
> are valid. But if someone want to use non-standard path separator (like /)
> FOO/>
> FOO/*/BAR
> wildcards in won't work. Also, policy, security and other settings that use them will
also be ignored.
> The easiest way to support this is to create a plugin that will convert destination names
using non-standard path separator to default one, so clients can use whatever convention they
want and broker config remains the same.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message