[jira] Commented: (UIMA-1695) Eclipse tooling: CDE fully instantiates components of aggregates, resulting in OutOfMemory issues

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

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

Marshall Schor commented on UIMA-1695:
--------------------------------------

The CDE is using the base UIMA framework to get the metadata.  During this operation, the CDE does not instantiate the components (unless there's a bug... ).  

Even during the full-blown "validation" of the descriptors (done just before "saving"), the CDE is invoking the base UIMA framework in  special mode to prevent instantiation.  So, for instance, the UIMA framework has code saying: ....doFullValidation() - methods in the framework which according to the javadocs (See ResourceCreationSpecifier) 

bq.essentially performs all operations necessary to instantiate a Resource except that it does not actually instantiate the implementation class. If appropriate, this method will also attempt to create a CAS based on the descriptor, in order to do full type system verification.

So, more investigation is warrented :-)  I'll take a look.

> Eclipse tooling: CDE fully instantiates components of aggregates, resulting in OutOfMemory issues
> -------------------------------------------------------------------------------------------------
>
>                 Key: UIMA-1695
>                 URL: https://issues.apache.org/jira/browse/UIMA-1695
>             Project: UIMA
>          Issue Type: Improvement
>          Components: Eclipse plugins
>    Affects Versions: 2.3
>            Reporter: Thilo Goetz
>            Priority: Minor
>
> When I create an aggregate descriptor from several installed pears (e.g., WS tokenizer, tagger & regex), the CDE creates an OOM situation on Eclipse 3.5 and Sun Java 6 on windows.  This seems to be due to the fact that the CDE fully instantiates delegate components to get at their metadata.  Is this really necessary?  We keep all our metadata in xml specifically so we don't have to do this.

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