You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@tomee.apache.org by "Brett E. Meyer (JIRA)" <ji...@apache.org> on 2014/08/27 22:48:59 UTC

[jira] [Commented] (TOMEE-393) Provide remote JNDI access to JMS resources

    [ https://issues.apache.org/jira/browse/TOMEE-393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14112812#comment-14112812 ] 

Brett E. Meyer commented on TOMEE-393:
--------------------------------------

This works well for ConnectionFactory, etc.  However, topics and queues are still not working.  Ex:

<Resource id="sramp/events/topic" type="javax.jms.Topic"/>

Shouldn't that be exposed externally to "sramp/events/topic"?

> Provide remote JNDI access to JMS resources
> -------------------------------------------
>
>                 Key: TOMEE-393
>                 URL: https://issues.apache.org/jira/browse/TOMEE-393
>             Project: TomEE
>          Issue Type: New Feature
>            Reporter: Tim Haley
>            Assignee: Romain Manni-Bucau
>              Labels: JMS, JNDI
>             Fix For: 1.5.1
>
>
> JMS Resources defined in tomee.xml should be accessible from client applications running in a separate JVM on the same or a remote machine.



--
This message was sent by Atlassian JIRA
(v6.2#6252)