manifoldcf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karl Wright (JIRA)" <>
Subject [jira] [Commented] (CONNECTORS-1077) Add activity logging for decision and exception events across all connectors
Date Mon, 20 Oct 2014 11:50:33 GMT


Karl Wright commented on CONNECTORS-1077:

Hi Muhammed,

Just in case you weren't clear, I think it's fine to have connector-specific result codes.
 The rule should be that IF there's a common result code that would be a good fit, the common
one should be used.  Otherwise, the code should be connector-specific (and defined within
the connector itself).

For example, for the Tika extractor, there are three different kinds of exceptions it can
throw: TikaException, IOException, and SAXException.  I have result codes for all three of
these, but I have the IOEXCEPTION result code being in IOutputHistoryActivity because it is
likely to be seen elsewhere as well.  We *could* just have a general EXCEPTION result code
for all of these, but it's not clear to me under what conditions various exception types might
be thrown, so I'm a little bit unsure what the right thing to do is there.

> Add activity logging for decision and exception events across all connectors
> ----------------------------------------------------------------------------
>                 Key: CONNECTORS-1077
>                 URL:
>             Project: ManifoldCF
>          Issue Type: Improvement
>          Components: Alfresco connector
>    Affects Versions: ManifoldCF 2.0
>            Reporter: Karl Wright
>            Assignee: Karl Wright
>             Fix For: ManifoldCF 2.0
> Many document skip decisions or transient exceptions are only logged, and are not recorded
as history events.  This makes it necessary upon occasion to refer to the manifoldcf log for
basic diagnosis.  We should record activity events for most decisions and exceptions in the

This message was sent by Atlassian JIRA

View raw message