[
https://issues.apache.org/jira/browse/STANBOL-8?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13140315#comment-13140315
]
Florent ANDRE commented on STANBOL-8:
-------------------------------------
Witch format for the "enhancement report" we can imagine ?
Do we store this report in the Content Item ?
In the camel implementation, depending on the route defined, some engines could
be not enabled at the time of processing. Camel offer a way to deal with such
errors, and (have to be check in details) to do some business logic when errors
appears.
> Define/implement error handling strategy for EnhancementJobManager
> ------------------------------------------------------------------
>
> Key: STANBOL-8
> URL: https://issues.apache.org/jira/browse/STANBOL-8
> Project: Stanbol
> Issue Type: Improvement
> Components: Enhancer
> Reporter: Rupert Westenthaler
>
> The Interface does not define how to handle EngineExceptions of single
> engines while enhancing parsed content Items.
> The InMemoryJobManager implementation just forwards such exception what
> causes the whole enhancement request to fail if a single Engine encounters an
> exception. This might be the intended behavior in some cases, but might be
> unintended under other conditions. Especially on errors within semantic
> lifting type enhancement engines it might still make sense to return
> enhancement results of previous engines.
> One possible way would also to include an "enhancement report" in the
> response that provides information about errors and warnings during the
> enhancement process. This might be also a nice feature for the still
> unimplemented async. enhancement mode, because than such a report could also
> contain a listing of expected, but still missing enhancement results.
> best
> Rupert Westenthaler
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
