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

Posted to dev@aries.apache.org by "Guillaume Nodet (JIRA)" <ji...@apache.org> on 2018/02/20 21:20:00 UTC

[jira] [Resolved] (ARIES-1694) Allow JNDI factories to be forced in if already set

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

Guillaume Nodet resolved ARIES-1694.
------------------------------------
       Resolution: Fixed
         Assignee: Thomas Watson
    Fix Version/s: jndi-core-1.1.0

> Allow JNDI factories to be forced in if already set
> ---------------------------------------------------
>
>                 Key: ARIES-1694
>                 URL: https://issues.apache.org/jira/browse/ARIES-1694
>             Project: Aries
>          Issue Type: Bug
>          Components: JNDI
>            Reporter: Thomas Watson
>            Assignee: Thomas Watson
>            Priority: Major
>             Fix For: jndi-core-1.1.0
>
>
> While calling the factory setters on NamingManager the code currently gives up:
> NamingManager.setInitialContextFactoryBuilder(builder);
> NamingManager.setObjectFactoryBuilder(builder);
> In some cases it is desired to override the currently set builders.  A new option should be added to enable forcing in our own builders.  This should not be enabled by default.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)