[
https://issues.apache.org/jira/browse/STANBOL-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13145280#comment-13145280
]
Rupert Westenthaler commented on STANBOL-371:
---------------------------------------------
I think it would be better to implement this by
* supporting multiple JobManger services
* add an implementation that supports chains (there might be several different)
* add the Chain(s) supported by an instance as OSGI property (e.g.
"org.apache.stanbol.enhancer.chain")
Clients that want to enhance a ContentIem by using a specific chain could than
use a Filter like:
(&
(objectClass=org.apache.stanbol.enhancer.servicesapi.JobManager)
(org.apache.stanbol.enhancer.chain={chain-name})
)
this would inject/find/track the JobManager instance for a specific chain.
WDYT
> Change Jobmanager api to take care of chains
> --------------------------------------------
>
> Key: STANBOL-371
> URL: https://issues.apache.org/jira/browse/STANBOL-371
> Project: Stanbol
> Issue Type: Sub-task
> Components: Enhancer
> Reporter: Florent ANDRE
>
> In order to allow jobmanager to act depending on the chain, the following api
> method will be added to JobManager :
> void enhanceContent(ContentItem ci, String chain) throws EngineException;
> Have to see if
> void enhanceContent(ContentItem ci) throws EngineException;
> will be deprecated.
--
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
