[jira] Commented: (UIMA-1466) Instantiating top level pearSpecifier: reconfigure throwing NPE and need to set Session

["Marshall Schor (JIRA)" <ui...@incubator.apache.org>]

    [ https://issues.apache.org/jira/browse/UIMA-1466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12736725#action_12736725 ] 

Marshall Schor commented on UIMA-1466:
--------------------------------------

I discussed this with Adam, and it seems the right approach is to keep the PearSpecifier as a ResourceServiceSpecifier, because the actual pear specifier itself does not have things like parameter specifications - those are inside the contained AE, not part of the pear specifier.

Instead, we will extend the implementation of the pear wrapper so that it forwards calls, not just reconfigure, but other ones in the AnalysisEngineImplBase and ConfigurableResource interfaces to the contained AE.  That will make it possible, for instance, to programatically set parameters in the contained AE, which isn't otherwise possible.  

> Instantiating top level pearSpecifier: reconfigure throwing NPE and need to set Session
> ---------------------------------------------------------------------------------------
>
>                 Key: UIMA-1466
>                 URL: https://issues.apache.org/jira/browse/UIMA-1466
>             Project: UIMA
>          Issue Type: Bug
>          Components: Core Java Framework
>    Affects Versions: 2.2.2
>            Reporter: Marshall Schor
>            Assignee: Marshall Schor
>             Fix For: 2.3
>
>
> A user reported these two issues when trying to run a top level pear.  See http://markmail.org/thread/jbacko4l6jyonzse 
> A discussion with Adam L indicates the problem may be being caused by the fact that the PearSpecifier interface extends the ResourceServiceSpecifier, and things would work better if it extended the ResourceCreationSpecifier - in that the cause of the NPE which is a null value for the map representing the configuration parameters, in the method ConfigurationManagerImplBase.validateConfigurationParameterSettings.  This map is setup by Resource_ImplBase if the specifier is a subtype of ResourceCreationSpecfier, but not otherwise.
> Also, the *session* is setup, but again, only if the specifier is a subtype of ResourceCreationSpecifier.  So, the first thing to investigate is to see if we can switch this, and what the impact would be.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.