[
https://issues.apache.org/jira/browse/STANBOL-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13156604#comment-13156604
]
Enrico Daga commented on STANBOL-343:
-------------------------------------
The Jobs API have been moved to a dedicated module: Stanbol Commons Jobs (see
STANBOL-383). The /reasoners endpoint implements this api.
A set of runtime tests on the services have been prepared in /services-test, a
shared class between runtime tests is in /test. Some of these (offline ones)
could be added to the shares integration-tests module, after putting Reasoners
in the full launcher (but decoupling of i-t from a single module is in
discussion STANBOL-289).
Tests are actually configured to run with a kres launcher (so you need to build
that before running the tests).
At this stage I would move this to /trunk, close this issue and then create
dedicated issues for improvements.
> Long term operations (Jobs) for reasoning services
> --------------------------------------------------
>
> Key: STANBOL-343
> URL: https://issues.apache.org/jira/browse/STANBOL-343
> Project: Stanbol
> Issue Type: Improvement
> Components: Reasoners
> Reporter: Enrico Daga
> Assignee: Enrico Daga
>
> The current implementation of the reasoning services execute the operation in
> real time.
> Reasoning tasks are often time consuming, and in some cases cannot be
> completed in the lifetime of a http request.
> For this reason, there is the need of a way of running reasoning operations
> in the background, and a web service to ping the running operation and
> retrieve the result, when ready.
--
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
