[jboss-jira] [JBoss JIRA] Commented: (JBAS-6013) Support createDestination in jboss/message-driven

[Filip Hrbek (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBAS-6013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12440176#action_12440176 ] 

Filip Hrbek commented on JBAS-6013:
-----------------------------------

How do I create such a queue using @MessageDriven annotation only? I tried to build latest jboss where I could find all the new stuff but could not figure out how to do this.

> Support createDestination in jboss/message-driven
> -------------------------------------------------
>
>                 Key: JBAS-6013
>                 URL: https://jira.jboss.org/jira/browse/JBAS-6013
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: EJB2, EJB3
>            Reporter: Adrian Brock
>            Assignee: Adrian Brock
>             Fix For: JBossAS-5.0.0.GA
>
>
> In the old JMSContainerInvoker there was a flag called "createJBossMQDestination"
> which allowed the MDB to automatically create the JMS destination.
> This has is no longer supported with the reworking of the metadata and changes to the MDB container.
> To re-introduce this behaviour and resolve some of the issues we had with this feature (which lead
> to it being disabled by default), the behaviour should be made pluggable via a deployer instead.
> Issues this will resolve over the previous implementation:
> 1) The Destination will be removed at undeployment
> 2) The Destination construction method can be replaced by switiching the deployer, e.g. for different backend jms servers
> including understanding rar specific activation config properties
> 3) The behaviour is not necessarily JMS specific, e.g. other inbound adapters could create their own destinations
> The legacy "createJBossMQDestination" will still be checked when it exists.

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