You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Richard Eckart de Castilho (JIRA)" <de...@uima.apache.org> on 2016/09/09 17:48:23 UTC
[jira] [Updated] (UIMA-52) Provide hooks in processing chain to
allow monitoring/debugging
[ https://issues.apache.org/jira/browse/UIMA-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Richard Eckart de Castilho updated UIMA-52:
-------------------------------------------
Labels: Stale (was: )
This issue is marked as "stale" due to inactivity for 5 years or longer. If no further activity is detected on this issue, it is scheduled be closed as 'unresolved' in 3 months time from now (Dec 2016).
> Provide hooks in processing chain to allow monitoring/debugging
> ---------------------------------------------------------------
>
> Key: UIMA-52
> URL: https://issues.apache.org/jira/browse/UIMA-52
> Project: UIMA
> Issue Type: Wish
> Components: Core Java Framework
> Reporter: Adam Lally
> Priority: Minor
> Labels: Stale
>
> User requests that we provide callback hooks at relevant points in the execution of an AnalysisEngine:
> For example for a primitive AE deployed as a service:
> CAS received -> CAS deserialized -> typeSytemInit() called -> process() called -> CAS serialized --> CAS emitted.
> For an Aggregate, there could also be notifications when each component AE is called.
> The user also thinks it would be useful to register for notifications pertaining only to a particular CAS instance.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)