[
https://issues.apache.org/jira/browse/ACTIVEMQ6-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14265140#comment-14265140
]
Fredrik Jonson commented on ACTIVEMQ6-13:
-----------------------------------------
Is this issue trying to resolve the same issue as
https://issues.jboss.org/browse/HORNETQ-302 (Consider allowing creation of
destinations via the pure JMS API)? Please disregard my off topic chatter below
otherwise. :)
If it is, you probably want to look into how ActiveMQ 5.x does it. AFAIK, in
AMQ5 the JMS api Session.createQueue() methods does not communicate with the
server, so the queues are created only when the first message is received by
the broker. This saves a small amount of overhead in the createQueue method
call. Nice, IMO! (Yes, you might argue that repetetive calls to createQueue is
an antipattern, but it happens anyway.)
https://github.com/apache/activemq/blob/trunk/activemq-client/src/main/java/org/apache/activemq/ActiveMQSession.java#L1264
AMQ5 users also expect the queues to be durable and non-temporary, i.e not
removed when unsubscribed. I do not recall if you can configure thesese
caracteristincs though.
> Investigate auto destination creation support
> ---------------------------------------------
>
> Key: ACTIVEMQ6-13
> URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-13
> Project: Apache ActiveMQ 6
> Issue Type: New Feature
> Reporter: Martyn Taylor
> Assignee: Justin Bertram
> Fix For: 6.0.0
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
