[jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-322) Deploying an MDB for a destination that doesn't exist fails.

[Tim Fox (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-322?page=all ]

Tim Fox closed JBMESSAGING-322.
-------------------------------

    Resolution: Won't Fix
      Assignee: Tim Fox

This is a non issue.

The JMSContainerInvoker only attempts to create a JBossMQ destination if the attribute "createJBossMQDestination" is true.

The JBM installation guide clearly states to set this to false.

What's more even if this was an issue, it should be an issue for the AS project not JBM.

> Deploying an MDB for a destination that doesn't exist fails.
> ------------------------------------------------------------
>
>                 Key: JBMESSAGING-322
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-322
>             Project: JBoss Messaging
>          Issue Type: Sub-task
>          Components: AS Integration
>    Affects Versions: 1.0.0
>            Reporter: Ovidiu Feodorov
>         Assigned To: Tim Fox
>             Fix For: 1.4.0.CR1
>
>   Original Estimate: 4 hours
>  Remaining Estimate: 4 hours
>
> If the destination an MDB is configured with doesn't exist, the MDB Container's JMSContainerInvoker tries to create the destination and fails because uses a non-portable interface that only works with JBossMQ.
>  Line 1201, org.jboss.ejb.plugins.jms.JMSContainerInvoker.createDestination()
>          // invoke the server to create the destination
>          server.invoke(new ObjectName("jboss.mq:service=DestinationManager"), .....
>          

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