[jira] Commented: (OPENEJB-1331) Global, app, or module jndi contexts are not always linked with ejb's jndi context

["Jarek Gawor (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/OPENEJB-1331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12899476#action_12899476 ] 

Jarek Gawor commented on OPENEJB-1331:
--------------------------------------

Committed fixes to trunk in revision 986399. The code tries to bind app/AppName and module/ModuleName if available and otherwise adds a dummy object in order to ensure the bindings are non-empty. 

I'm open to suggestions if there is some other way to avoid the dummy object.


> Global, app, or module jndi contexts are not always linked with ejb's jndi context
> ----------------------------------------------------------------------------------
>
>                 Key: OPENEJB-1331
>                 URL: https://issues.apache.org/jira/browse/OPENEJB-1331
>             Project: OpenEJB
>          Issue Type: Bug
>          Components: deployment
>    Affects Versions: 3.0-beta-1
>            Reporter: Jarek Gawor
>            Assignee: Jarek Gawor
>             Fix For: 3.2
>
>
> The global, app, or module jndi contexts are not always linked with the ejb's jndi context. That's because these contexts might be empty when they are first created and therefore will not be linked with the ejb's jndi context (see EnterpriseBeanBuilder.bind()).
> The simplest solution is to ensure that these contexts are always non-empty.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.