[
https://issues.apache.org/jira/browse/STANBOL-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13189687#comment-13189687
]
Rupert Westenthaler commented on STANBOL-431:
---------------------------------------------
HI all
I am getting in a state where a lot of the things described in
http://stanbol.staging.apache.org/stanbol/docs/trunk/enhancer/STANBOL-414-specification.html
are implemented. To be fair all of the new features not covered by existing
unit/integration tests is only barely tested. But I can also report that all
the current tests run fine on top of the new infrastructure.
Because of that I would suggest that I do commit a first version this work to
give everybody a change to continue his work based on the new
possibilities/features provided by this.
Here a Overview about the current state:
Implemented:
* EventJobManager: EnhancementJobManager implementation that supports Chains
and in parallel execution of engines using the org.osgi.services.event framework
* RESTful interface "/enhancer/chain/<chain>": Allows to use the same RESTful
interface as currently supported for "/engines" on any configured enhancement
chain
* Chain implementations: WeightedChain, GraphChain, DefaultChain
* EnhancementEngine: Added getName() and the "stanbol.enhancer.engine.name" to
all currently available engine implementations. Singeltons do have a default
value configured. For engines that support multiple instances the name
@property was added
* EnhancementEngineManager implementation (both as OSGI service and as
ServiceTracker like utility)
* ChainManager implementation (both as OSGI service and as ServiceTracker like
utility)
The main missing parts are:
* adapt current Engines to support ASYNC mode
* add enhancement metadata to the ContentItem
* RESTful Interfaces for
* /enhancer/chain (root resource providing infos for all running chains)
* /enhancer/engine (root resource providing infos for all running engines)
* /enhancer/engine/<engine> (resource allowing to sent requests to single
engines)
* re-purpose the outdated "weightedjobmanager" to an implementation that
enhances a ContenItem synchronously
* Unit tests for the ExecutionPlan utilities
* Integration tests for enhancement Chains
WDYT
Rupert
> Improve Enhancer/ REST endpoint
> -------------------------------
>
> Key: STANBOL-431
> URL: https://issues.apache.org/jira/browse/STANBOL-431
> Project: Stanbol
> Issue Type: Improvement
> Components: Enhancer
> Reporter: Florent ANDRE
>
> From STANBOL-414, Reto :
> Rest
> /enhancer
> /enhancer/engine/<engineId>
> /enhancer/chains/<chainId>
> - query params:
> Optional inputWithMetadata -> expects multipart/mime with 2 sections of which
> the first is rdf
> Optional outputWithContentParts[=<section-ordinal>] -> the result is
> multipart (instead of rdf) containing rdf as the first section and the parts
> in the second section, if there is more than one part this second section is
> itself multipart, this argument might be repated to have different sections
> Optional omitMetada -> no metadate in the result, makes only sense with
> outputContentParts argument, the result will correspond to the second section
> of the malipart returned without this argument
--
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
