Hi Benjamin, Reto > the web and engine bundles can not (log messages: > https://gist.github.com/groe/208536f121ea562e1d09). [..] > visiting http://localhost:8080/topic we only get this error > message: https://gist.github.com/groe/d0acf569ec719947ee89
Looks like as if the web module of the TopicEngine is not yet converted to the new commons-web (of the trunk). @Reto can you confirm this? In that case I would recommend you to use the stable "release-0.12" branch [1] instead. > However all the > default chains seem to create Text-/TopicAnnotations only but not a > single TopicAnnotation The TopicEngine is not included by default. This is mainly because Stanbol does currently not come with an pre-trained model. To use the Engine you will need to install the additional bundles. But even without an pre-trained model there is IMO no reason why the TopicEngine should not be included in the default launcher(s) of for the 0.12 release. I will create an according issue and perform the required changes in the launcher configurations. > the topic engine now seems to be splitted up in 3 parts > (api, web and engine). Correct. This split was done as part of STANBOL-1142 [2] best Rupert [1] http://svn.apache.org/repos/asf/stanbol/branches/release-0.12/ [2] https://issues.apache.org/jira/browse/STANBOL-1142 On Mon, Nov 18, 2013 at 6:54 PM, Benjamin Grössing <e1025...@student.tuwien.ac.at> wrote: > Hello, > > I am currently working on an open source project and we would like to > use Stanbol in order to find matching keywords/topics for web sites > (i.e. content classification). However, we are having some troubles > setting up Stanbol in the right way - maybe someone here could help > us? > > What we have done so far: Build and start stanbol from SVN trunk > according to the "Getting Started Tutorial" and do some quick > enhancement queries - which works perfectly fine (after updating the > maven config to use maven-shade 2.1 instead of 2.0 - there seems to be > an incompatibility with maven 3.1.1 otherwise). However all the > default chains seem to create Text-/TopicAnnotations only but not a > single TopicAnnotation (which would be the kind of annotation which > would fit our needs best, if I understand the docs correctly). > > So we found the topic engine > (http://www.iks-project.eu/sites/default/files/Topic-Classification.pdf) > and tried to install it. However, we encountered a few problems with > that: > -) The paths mentioned in the docs (see PDF link) are a little > different and the topic engine now seems to be splitted up in 3 parts > (api, web and engine). Okay, so we installed all three of them. > -) While the topic API bundle can be started, the web and engine > bundles can not (log messages: > https://gist.github.com/groe/208536f121ea562e1d09). So, the packages > "javax.ws.rs..." and "org.apache.stanbol.enhancer.topic" seem to be > missing. We tried some things to get that to work as well (like > removing this from the pom.xml of the engine bundle: > https://gist.github.com/groe/1bb119dc7e04ae29b40e and adding > "jsr311-api" as a maven dependency for the javax.ws.rs package), and > eventually all three bundles were installed (although not sure if > correctly). > -) With everything installed we have created the topic engine > configuration (as described in the PDF). But when visiting > http://localhost:8080/topic we only get this error message: > https://gist.github.com/groe/d0acf569ec719947ee89 > > Now we don't know what else we can try. Is this an actual (known?) > problem with the topic engine? Is it still maintained at all? Any > chances of getting it to run? > > Any help would be greatly appreciated! > > Regards > Benjamin Groessing -- | Rupert Westenthaler rupert.westentha...@gmail.com | Bodenlehenstraße 11 ++43-699-11108907 | A-5500 Bischofshofen
