You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tomee.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/06/29 08:40:00 UTC

[jira] [Commented] (TOMEE-2083) IvmContext list doesn't list all bindings in case of federated contexts

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

ASF GitHub Bot commented on TOMEE-2083:
---------------------------------------

GitHub user katya-stoycheva opened a pull request:

    https://github.com/apache/tomee/pull/81

    [TOMEE-2083] List IvmContext should list all of its federated context bindings

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/katya-stoycheva/tomee module-bindings-not-visible-from-comp

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/tomee/pull/81.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #81
    
----
commit dbaf157d210458ae83bb7bd1fb5083f0030c945d
Author: Katya Todorova <ka...@gmail.com>
Date:   2017-06-29T08:35:32Z

    List IvmContext should list all of its federated context bindings

----


> 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)