[UIMA-6386] Wrong session set on ConfigurationManager in aggregates

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.3.0SDK
• Component/s: Core Java Framework
• Assignee: Richard Eckart de Castilho
• Reporter: Richard Eckart de Castilho
• Created: 06/Oct/21 17:04
• Updated: 02/May/22 13:00
• Resolved: 08/Oct/21 07:37

Description

When initializing a component, then Resource_ImplBase sets the Session of the ConfigurationManager of the current UimaContext using the Session of the current UimaContext:

{org.apache.uima.resource.Resource_ImplBase.initialize(ResourceSpecifier, Map<String, Object>)}

        mUimaContextAdmin.getConfigurationManager()
                .setSession(mUimaContextAdmin.getSession());

However, this can set the wrong session on the

{ConfigurationManager}. In a hierarchy of {UimaContexts}, there is only one {ConfigurationManager}

associated with the

{RootUimaContext_impl}. The {ChildUimaContext_impl} delegate to their respective root in their {getConfigurationManager()} methods.

So far so good.

But the {Session} of returned by {ChildUimaContext_impl.getSession()} is a scoped {SessionNamespaceView_impl} instance which limits the view to the parameters applicable to the child context. The problematic lines above cause this scoped session view to be injected into the {ConfigurationManager} of the {RootUimaContext_impl}

which can cause configuration parameters at the root level to become inaccessible.

At least, the code would need to be changed to

        mUimaContextAdmin.getConfigurationManager()
                .setSession(mUimaContextAdmin.getRootContext().getSession());

but instead of doing that, the code could probably also be change to inject the session when creating the

{RootUimaContext_impl}

in the first place.

Issue Links

• links to: GitHub Pull Request #144
• links to: GitHub Pull Request #148