[
https://issues.apache.org/jira/browse/TOMEE-3726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Zowalla closed TOMEE-3726.
----------------------------------
Fix Version/s: 11.0.0
10.3.0
Resolution: Fixed
Fixed in https://github.com/apache/tomee/commit/482804b46f (main) and
https://github.com/apache/tomee/commit/b7d7a3f6de (tomee-10.x).
> Queue is visible in JNDI Tree (java://id-resource)
> --------------------------------------------------
>
> Key: TOMEE-3726
> URL: https://issues.apache.org/jira/browse/TOMEE-3726
> Project: TomEE
> Issue Type: Bug
> Components: TomEE Core Server
> Affects Versions: 8.0.6
> Environment: Windows 10 Prof.
> Reporter: Andreas
> Priority: Minor
> Fix For: 11.0.0, 10.3.0
>
>
> 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.20.10#820010)
