[jboss-jira] [JBoss JIRA] (WFLY-2380) DefaultJMSConnectionFactory binding must be accessing from application client deployment

[Eduardo Martins (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-2380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12824922#comment-12824922 ] 

Eduardo Martins edited comment on WFLY-2380 at 10/25/13 4:02 AM:
-----------------------------------------------------------------

same applies to the default data source and EE concurrency resources, created WFLY-2382 to fix these
                
      was (Author: emmartins):
    same applies to the default data source and EE concurrency resources, created WFLY-2382 to fix the "others"
                  
> DefaultJMSConnectionFactory binding must be accessing from application client deployment
> ----------------------------------------------------------------------------------------
>
>                 Key: WFLY-2380
>                 URL: https://issues.jboss.org/browse/WFLY-2380
>             Project: WildFly
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: JMS
>            Reporter: Jeff Mesnil
>            Assignee: Jeff Mesnil
>             Fix For: 8.0.0.CR1
>
>
> According to the spec (and TCK), an application client deployment must be able to look up the default JMS Connection Factory from "java:comp/DefaultJMSConnectionFactory" but this binding is no longer added to the module description in DefaultJMSConnectionFactoryBindingProcessor.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira