You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@aries.apache.org by "Valentin Mahrwald (JIRA)" <ji...@apache.org> on 2011/02/03 22:18:28 UTC

[jira] Resolved: (ARIES-540) DelegateContext is too eager in caching URL contexts

     [ https://issues.apache.org/jira/browse/ARIES-540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Valentin Mahrwald resolved ARIES-540.
-------------------------------------

    Resolution: Fixed

Changes committed in #1059795.

> DelegateContext is too eager in caching URL contexts
> ----------------------------------------------------
>
>                 Key: ARIES-540
>                 URL: https://issues.apache.org/jira/browse/ARIES-540
>             Project: Aries
>          Issue Type: Bug
>          Components: JNDI
>    Affects Versions: 0.3
>            Reporter: Valentin Mahrwald
>            Assignee: Valentin Mahrwald
>
> In some enterprise integration scenarios, it is not appropriate to cache URL contexts. For example java:comp env lookups can depend on thread contexts and return different results for the same InitialContext when used from inside different EJBs.
> To maintain a level of performance we can still cache the ObjectFactory that creates the URL context and so avoid service registry lookups.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira