[
https://issues.apache.org/jira/browse/OPENEJB-2151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas resolved OPENEJB-2151.
------------------------------
Resolution: Duplicate
False project, move to tomee
> Queue is visible in the JNDI Tree of ejbd
> -----------------------------------------
>
> Key: OPENEJB-2151
> URL: https://issues.apache.org/jira/browse/OPENEJB-2151
> Project: OpenEJB
> Issue Type: Bug
> Components: connectors
> Environment: open-ejb-standalone 8.0.6
> Windows 10 Prof.
> Reporter: Andreas
> Priority: Minor
>
> Hi,
> In *line 316* of *org.apache.openejb.server.ejbd.JndiRequestHandler* you use
> *java.util.Queue* instead *javax.jms.Queue* to compare (instaceof) the Object
> loaded from JNDITree.
> The bug results in the following consequence:
> If you have configured a *Queue* as resource, you can call this queue by a
> remote client (over RemoteInitialFactory->jndi-name: java://id-resource).
> In contrast a *Topic* you cannot called by this way (results in null as
> instance).
> The method "*doLookup(final JNDIRequest req, final JNDIResponse res, final
> String prefix)*" returns for a Queue *JNDI_OK* an for a Topic *JNDI_RESOURCE*
> as result.
> So you can get a queue remote from the ejbd connector (not the right way i
> think) and a topic not.
> Greetings
> Andreas Riesel
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
