[
https://issues.apache.org/jira/browse/UIMA-5032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15399471#comment-15399471
]
Marshall Schor commented on UIMA-5032:
--------------------------------------
Component initialization has 2 parts:
* getting / merging type system information
* running the "initialize()" method
If, at "startup" time, the framework could be "told" which items to skip, then
it could avoid both of these.
This proposition appears to indicate a use case where the decision on which
items to skip needs to be done dynamically, at "run" time, is that correct? If
so, then only the 2nd part of initialization would be skipped.
It seems a better approach might be to have a spec for feature toggles,
available at startup time, that would bypass parts not wanted, because then
both parts of the initialization could be bypassed.
> Support feature toggle using lazy annotator initialization
> -----------------------------------------------------------
>
> Key: UIMA-5032
> URL: https://issues.apache.org/jira/browse/UIMA-5032
> Project: UIMA
> Issue Type: Improvement
> Components: Core Java Framework
> Reporter: Eddie Epstein
>
> Feature toggle is a useful technique to have a single source stream for both
> production and development activities. One approach for UIMA to help support
> feature toggle would be to do component initialization only on the first
> process call. Lazy initialization would allow flow controller configuration
> to easily turn components on and off.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
