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

Posted to dev@aries.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2017/02/23 16:44:44 UTC

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=15880813#comment-15880813 ] 

ASF subversion and git services commented on ARIES-1694:
--------------------------------------------------------

Commit 1784171 from tjwatson@apache.org in branch 'aries/trunk'
[ https://svn.apache.org/r1784171 ]

[ARIES-1694] - Allow JNDI factories to be forced in if already set

> 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
>
> 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
(v6.3.15#6346)