Hello Rupert,

thanks a lot for your quick response and the bug fix in STANBOL-1142!
I have switched to branch release-0.12 and building, installing and
running the topic engine now works like charm.

Unfortunately when I follow the tutorial [1] and do the next step,
which is executing "curl -X POST --data @skos.rdf.xml
http://localhost:8080/topic/model/dbpedia-category-model"; with
skos.rdf.xml from [2], the response is "HTTP ERROR: 415". The server
log shows this: [3].  POSTing single concepts works; the error only
occurs for the RDF/XML file.

Do you have any idea what I might be doing wrong?

Regards
Benjamin Groessing

[1] http://www.iks-project.eu/sites/default/files/Topic-Classification.pdf
[2] http://www.w3.org/TR/skos-reference/skos.rdf
[3] https://gist.github.com/groe/94494930d6dcae2f9719

2013/11/19 Rupert Westenthaler <rupert.westentha...@gmail.com>:
> Hi Benjamin
>
> While adding the TopicEngine modules to the Enhancer bundlelist [3] I
> noticed that there is indeed a failure in the pom.xml file of the
> topic engine module that also affects the 0.12 releasing branch. This
> is the error referenced by your original message with
>
> On Mon, Nov 18, 2013 at 6:54 PM, Benjamin Grössing
> <e1025...@student.tuwien.ac.at> wrote:
>> 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
>
> As this was introduced by STANBOL-1142 [2] I will reopen this issue to
> correct this in both the 0.12 releasing branch as well as the trunk.
>
> Thanks for reporting this. Its always good to fix issues like that
> before an upcoming release!
>
> best
> Rupert
>
>> [1] http://svn.apache.org/repos/asf/stanbol/branches/release-0.12/
>> [2] https://issues.apache.org/jira/browse/STANBOL-1142
> [3] https://issues.apache.org/jira/browse/STANBOL-1213
> --
> | Rupert Westenthaler             rupert.westentha...@gmail.com
> | Bodenlehenstraße 11                             ++43-699-11108907
> | A-5500 Bischofshofen
>

Reply via email to