You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Jeremy Hughes (JIRA)" <ji...@apache.org> on 2014/09/12 12:31:34 UTC

[jira] [Assigned] (ARIES-1117) JNDI Environment Augmentation can cause problems with JNDI providers

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

Jeremy Hughes reassigned ARIES-1117:
------------------------------------

    Assignee: Jeremy Hughes

> JNDI Environment Augmentation can cause problems with JNDI providers
> --------------------------------------------------------------------
>
>                 Key: ARIES-1117
>                 URL: https://issues.apache.org/jira/browse/ARIES-1117
>             Project: Aries
>          Issue Type: Bug
>          Components: JNDI
>            Reporter: Simon Gormley
>            Assignee: Jeremy Hughes
>         Attachments: Unaugmentation.diff
>
>
> The JNDI Environment augmentation may be used to add the BundleContext to the Map used by JNDI to store the provider url etc. If the BundleContext is left in the Map, it can cause problems with the JNDI provider if, for example, the Map is serialized and deserialized elsewhere, as BundleContext may not exist. 
> A suggestion is to add an unaugmentation ability so that after Aries is done with the BundleContext, it can be removed from the Map, allowing providers to operate as though Aries wasn't involved.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)