[
https://issues.apache.org/jira/browse/ARTEMIS-1289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16088712#comment-16088712
]
ASF GitHub Bot commented on ARTEMIS-1289:
-----------------------------------------
Github user michaelandrepearce commented on the issue:
https://github.com/apache/activemq-artemis/pull/1400
@mtaylor as discussed in IRC, few comments i would have.
- Address is currently xsd:string already (this is just following suit)
- Duplicate declaration is checked anyhow on config load, do we really need
a complex schema? as we don't do this on address and the same applies, that it
must be unique.
- Queues can be declared in two places it seems according to the xsd,
either within an address, or within the queues section, as such an unique field
within one element would not capture where it could be defined in two separate
places.
> Unable to configure queues containing "/" in broker.xml
> -------------------------------------------------------
>
> Key: ARTEMIS-1289
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1289
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Reporter: Michael Andre Pearce
>
> "/" seems to be a valid address character and can be used as a separator. But
> when making queues with corresponding names such as for JMS Queues manually
> in broker.xml it is disallowed due to xsd:ID type, where as address name
> allows xsd:string. Like wise this doesn't cause issue if you create
> queues/address via client, as such seems just a schema type issue in the xsd.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
