[
https://issues.apache.org/jira/browse/STANBOL-1472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rafa Haro updated STANBOL-1472:
-------------------------------
Fix Version/s: (was: 1.0.0)
1.1.0
> i checked the tokenizer status but still it throw exception the tokenizer is
> not active.
> ----------------------------------------------------------------------------------------
>
> Key: STANBOL-1472
> URL: https://issues.apache.org/jira/browse/STANBOL-1472
> Project: Stanbol
> Issue Type: Bug
> Components: Enhancer
> Affects Versions: 0.12.0
> Environment: Ubuntu
> Reporter: sajjad khan afridi
> Priority: Major
> Labels: usability
> Fix For: 1.1.0
>
> Attachments: issue.png
>
>
> I successfully compiled and installed stanbol version 0.12.0. i started
> running jar file
> *org.apache.stanbol.launchers.full-0.12.1-SNAPSHOT.jar.*
> It was running good, but i faced an issue while using the enchancer engine on
> the provided interface. The below snapshot depict the issue. I also checked
> the Tokenizer engine at the OSGI console which was also an active and running
> state. I also tried to install the 1.0.0 version of the apache stanbol which
> run without tokenizer issue, but still i need the content hub and
> cmsadapter.please help me to sort out the depicted issue. I have another
> question how your development team maintain the content hub and cms adapter
> component in the launched version (1.0.0)?Is there any way to integrate the
> launch version component into the older version 0.12.0?
>
>
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
