You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tomee.apache.org by "Katya Todorova (JIRA)" <ji...@apache.org> on 2017/06/29 08:40:00 UTC
[jira] [Created] (TOMEE-2083) IvmContext list doesn't list all
bindings in case of federated contexts
Katya Todorova created TOMEE-2083:
-------------------------------------
Summary: IvmContext list doesn't list all bindings in case of federated contexts
Key: TOMEE-2083
URL: https://issues.apache.org/jira/browse/TOMEE-2083
Project: TomEE
Issue Type: Bug
Components: TomEE Core Server
Affects Versions: 7.0.3
Reporter: Katya Todorova
When a list/listBindings operation is performed from a context which reference a federated contexts, some of federated bindings are not listed.
IvmContext#MyNamingEnumeration#gatherNodes uses as parent the original IvmContext which is not the actual parent of the federated (sub)contexts. This affects the check (isMyChild returs false) for subcontexts and they are not listed as bindings.
For direct bindings (bound object is not a naming context) this is not applicable since they are added to the list of gathered not before recursive invocation of the gatherNodes method.
Real world scenario - when an env-entry is definedin the ejb deployment descriptor and it refers a subcontext of (for example) module/env, when listing the context (module/env), the env-entry is not found.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)