You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stanbol.apache.org by Rupert Westenthaler <ru...@gmail.com> on 2012/12/01 15:19:04 UTC

Re: DBPedia Spotlight Enhancer is not working

On Fri, Nov 30, 2012 at 2:14 PM, Rafa Haro <rh...@zaizi.com> wrote:
> Hi all,
>
> I was trying to test the DBPedia Spotlight enhancer with a local
> installation of DBPedia Spotlight in an out-of-the-box Stanbol from the
> repository. So, I changed the URL of the service in dbpspotlightannotate
> engine to my point to my local service endpoint. When I tested it, the
> enhancement chain always stopped at language detection engine. I thought
> that maybe there was any error with my local installation, but then I tried
> again with the default URL endpoint
> (http://spotlight.dbpedia.org/rest/annotate) and got the same result.

I have never tried to change the configuration of the service URL so
this might be a Bug. Is your Spotlight service public accessible. If
so I could try to replicate this. If you do not want send the URL on a
public mailing list feel free to send it directly to me.

>The
> only clue I have so far is the following message in the console where I run
> Stanbol:
> /
> //A servlet request, to the URI
> http://192.168.1.35:8080/enhancer/chain/dbpedia-spotlight, contains form
> parameters in the request body but the request body has been consumed by the
> servlet or a servlet filter accessing the request parameters. Only resource
> methods using @FormParam will work as expected. Resource methods consuming
> the request body by other means will not work as expected./
>

This message is triggered by any Request to Stanbol when the
"httpqueryheaders" module is active. It can not be the cause for your
problem.

Are there any loggings in the Stanbol log file?
What is the exact Chain configuration you are using?

On the Stanbol Dev Server [1] (nightly build) it seams to work.

best
Rupert

[1] http://dev.iks-project.eu:8081/enhancer/chain/dbpedia-spotlight

> Does anyone know what can be happening??
>
> Regards
>
> This message should be regarded as confidential. If you have received this
> email in error please notify the sender and destroy it immediately.
> Statements of intent shall only become binding when confirmed in hard copy
> by an authorised signatory.
>
> Zaizi Ltd is registered in England and Wales with the registration number
> 6440931. The Registered Office is 222 Westbourne Studios, 242 Acklam Road,
> London W10 5JJ, UK.



--
| Rupert Westenthaler             rupert.westenthaler@gmail.com
| Bodenlehenstraße 11                             ++43-699-11108907
| A-5500 Bischofshofen

Re: DBPedia Spotlight Enhancer is not working

Posted by Rupert Westenthaler <ru...@gmail.com>.
On Wed, Dec 5, 2012 at 1:09 PM, Rafa Haro <rh...@zaizi.com> wrote:
> Hi Rupert,
>
> I haven't been able to reproduce it using online dbpedia spotlight web
> service. The only way I know to trigger the exception is using a local
> installation of DBpedia Spotlight and loading a wrong spotting dictionary. I
> know that sounds very specific but I have tried other options and never get
> that exception again

Ok. I was just interested, because when we integrated Stanbol with the
LinkedMediaFramework we where also seeing "Caused by:
java.io.IOException: Stream closed" exceptions from time to time. We
where never completely sure about the cause for them (as they might be
also caused by the request being closed). However your issue suggest
that those exceptions can be indirectly caused by some other exception
within Stanbol what is definitely interesting and might be an
indication of some bug somewhere in the Stanbol commons.web modules.

best
Rupert

--
| Rupert Westenthaler             rupert.westenthaler@gmail.com
| Bodenlehenstraße 11                             ++43-699-11108907
| A-5500 Bischofshofen

Re: DBPedia Spotlight Enhancer is not working

Posted by Rafa Haro <rh...@zaizi.com>.
Hi Rupert,

I haven't been able to reproduce it using online dbpedia spotlight web 
service. The only way I know to trigger the exception is using a local 
installation of DBpedia Spotlight and loading a wrong spotting 
dictionary. I know that sounds very specific but I have tried other 
options and never get that exception again

Regards

El 05/12/12 06:32, Rupert Westenthaler escribió:
> Hi
>
>
>   Can you produce additional information on how to reproduce this. I
> tried some texts that give no results but those have not triggered
> this.
>
> best
> Rupert
>
> On Wed, Dec 5, 2012 at 12:06 AM, Pablo N. Mendes <pa...@gmail.com> wrote:
>> Just for clarity, the log message tells you (perhaps not clearly enough)
>> that the output of spotlight is empty:
>>
>> "//Información: Removed 1 (100 percent) spots using spotSelector
>> ChainedSelector//"
>>
>> However, there seems to be still a problem on Stanbol's side when no
>> results are returned. Even with perfectly installed DBpedia Spotlight, it
>> is conceivable that some piece of text will have no annotations (rare, but
>> possible). The enhancement engine should not break from that. From Rupert's
>> message I understand that he's on top of this issue, but I just wanted to
>> make sure that this is clear.
>>
>> Cheers
>> Pablo
>> On Dec 4, 2012 5:58 PM, "Rafa Haro" <rh...@zaizi.com> wrote:
>>
>>> Hi Rupert and Reto,
>>>
>>> Just wanted to let you know that finally the problem was produced by an
>>> empty output of DBpedia Spotlight due to a bad configuration in its side.
>>>
>>> Thanks for your help again
>>>
>>> Regards
>>>
>>> El 03/12/12 19:20, Rupert Westenthaler escribió:
>>>
>>>> Hi Reto, Rafa
>>>>
>>>> @Rafa: I do not thing this is related to the spotlight engine
>>>>
>>>> @Reto: Could this be related to the Stanbol Security. Is this already
>>>> active. Andreas Gruber was asking me about the same Exception earlier
>>>> today.
>>>>
>>>> On Mon, Dec 3, 2012 at 7:09 PM, Rafa Haro <rh...@zaizi.com> wrote:
>>>>
>>>>> //03.12.2012 18:54:25.738 *WARN* [1548445156@qtp-558009892-5]
>>>>> org.apache.felix.http.jetty /enhancer/chain/dbpedia-**spotlight
>>>>> (java.lang.RuntimeException: java.security.**PrivilegedActionException:
>>>>> java.io.IOException: Stream closed) java.lang.RuntimeException:
>>>>> java.security.**PrivilegedActionException: java.io.IOException: Stream
>>>>> closed//
>>>>>
>>>> best
>>>> Rupert
>>>>
>>>> --
>>>> | Rupert Westenthaler             rupert.westenthaler@gmail.com
>>>> | Bodenlehenstraße 11                             ++43-699-11108907
>>>> | A-5500 Bischofshofen
>>>>
>>> This message should be regarded as confidential. If you have received this
>>> email in error please notify the sender and destroy it immediately.
>>> Statements of intent shall only become binding when confirmed in hard copy
>>> by an authorised signatory.
>>>
>>> Zaizi Ltd is registered in England and Wales with the registration number
>>> 6440931. The Registered Office is 222 Westbourne Studios, 242 Acklam Road,
>>> London W10 5JJ, UK.
>>>
>>>
>
>

This message should be regarded as confidential. If you have received this email in error please notify the sender and destroy it immediately. Statements of intent shall only become binding when confirmed in hard copy by an authorised signatory.

Zaizi Ltd is registered in England and Wales with the registration number 6440931. The Registered Office is 222 Westbourne Studios, 242 Acklam Road, London W10 5JJ, UK.


Re: DBPedia Spotlight Enhancer is not working

Posted by Rupert Westenthaler <ru...@gmail.com>.
Hi


 Can you produce additional information on how to reproduce this. I
tried some texts that give no results but those have not triggered
this.

best
Rupert

On Wed, Dec 5, 2012 at 12:06 AM, Pablo N. Mendes <pa...@gmail.com> wrote:
> Just for clarity, the log message tells you (perhaps not clearly enough)
> that the output of spotlight is empty:
>
> "//Información: Removed 1 (100 percent) spots using spotSelector
> ChainedSelector//"
>
> However, there seems to be still a problem on Stanbol's side when no
> results are returned. Even with perfectly installed DBpedia Spotlight, it
> is conceivable that some piece of text will have no annotations (rare, but
> possible). The enhancement engine should not break from that. From Rupert's
> message I understand that he's on top of this issue, but I just wanted to
> make sure that this is clear.
>
> Cheers
> Pablo
> On Dec 4, 2012 5:58 PM, "Rafa Haro" <rh...@zaizi.com> wrote:
>
>> Hi Rupert and Reto,
>>
>> Just wanted to let you know that finally the problem was produced by an
>> empty output of DBpedia Spotlight due to a bad configuration in its side.
>>
>> Thanks for your help again
>>
>> Regards
>>
>> El 03/12/12 19:20, Rupert Westenthaler escribió:
>>
>>> Hi Reto, Rafa
>>>
>>> @Rafa: I do not thing this is related to the spotlight engine
>>>
>>> @Reto: Could this be related to the Stanbol Security. Is this already
>>> active. Andreas Gruber was asking me about the same Exception earlier
>>> today.
>>>
>>> On Mon, Dec 3, 2012 at 7:09 PM, Rafa Haro <rh...@zaizi.com> wrote:
>>>
>>>> //03.12.2012 18:54:25.738 *WARN* [1548445156@qtp-558009892-5]
>>>> org.apache.felix.http.jetty /enhancer/chain/dbpedia-**spotlight
>>>> (java.lang.RuntimeException: java.security.**PrivilegedActionException:
>>>> java.io.IOException: Stream closed) java.lang.RuntimeException:
>>>> java.security.**PrivilegedActionException: java.io.IOException: Stream
>>>> closed//
>>>>
>>> best
>>> Rupert
>>>
>>> --
>>> | Rupert Westenthaler             rupert.westenthaler@gmail.com
>>> | Bodenlehenstraße 11                             ++43-699-11108907
>>> | A-5500 Bischofshofen
>>>
>>
>> This message should be regarded as confidential. If you have received this
>> email in error please notify the sender and destroy it immediately.
>> Statements of intent shall only become binding when confirmed in hard copy
>> by an authorised signatory.
>>
>> Zaizi Ltd is registered in England and Wales with the registration number
>> 6440931. The Registered Office is 222 Westbourne Studios, 242 Acklam Road,
>> London W10 5JJ, UK.
>>
>>



-- 
| Rupert Westenthaler             rupert.westenthaler@gmail.com
| Bodenlehenstraße 11                             ++43-699-11108907
| A-5500 Bischofshofen

Re: DBPedia Spotlight Enhancer is not working

Posted by "Pablo N. Mendes" <pa...@gmail.com>.
Just for clarity, the log message tells you (perhaps not clearly enough)
that the output of spotlight is empty:

"//Información: Removed 1 (100 percent) spots using spotSelector
ChainedSelector//"

However, there seems to be still a problem on Stanbol's side when no
results are returned. Even with perfectly installed DBpedia Spotlight, it
is conceivable that some piece of text will have no annotations (rare, but
possible). The enhancement engine should not break from that. From Rupert's
message I understand that he's on top of this issue, but I just wanted to
make sure that this is clear.

Cheers
Pablo
On Dec 4, 2012 5:58 PM, "Rafa Haro" <rh...@zaizi.com> wrote:

> Hi Rupert and Reto,
>
> Just wanted to let you know that finally the problem was produced by an
> empty output of DBpedia Spotlight due to a bad configuration in its side.
>
> Thanks for your help again
>
> Regards
>
> El 03/12/12 19:20, Rupert Westenthaler escribió:
>
>> Hi Reto, Rafa
>>
>> @Rafa: I do not thing this is related to the spotlight engine
>>
>> @Reto: Could this be related to the Stanbol Security. Is this already
>> active. Andreas Gruber was asking me about the same Exception earlier
>> today.
>>
>> On Mon, Dec 3, 2012 at 7:09 PM, Rafa Haro <rh...@zaizi.com> wrote:
>>
>>> //03.12.2012 18:54:25.738 *WARN* [1548445156@qtp-558009892-5]
>>> org.apache.felix.http.jetty /enhancer/chain/dbpedia-**spotlight
>>> (java.lang.RuntimeException: java.security.**PrivilegedActionException:
>>> java.io.IOException: Stream closed) java.lang.RuntimeException:
>>> java.security.**PrivilegedActionException: java.io.IOException: Stream
>>> closed//
>>>
>> best
>> Rupert
>>
>> --
>> | Rupert Westenthaler             rupert.westenthaler@gmail.com
>> | Bodenlehenstraße 11                             ++43-699-11108907
>> | A-5500 Bischofshofen
>>
>
> This message should be regarded as confidential. If you have received this
> email in error please notify the sender and destroy it immediately.
> Statements of intent shall only become binding when confirmed in hard copy
> by an authorised signatory.
>
> Zaizi Ltd is registered in England and Wales with the registration number
> 6440931. The Registered Office is 222 Westbourne Studios, 242 Acklam Road,
> London W10 5JJ, UK.
>
>

Re: DBPedia Spotlight Enhancer is not working

Posted by Rafa Haro <rh...@zaizi.com>.
Hi Rupert and Reto,

Just wanted to let you know that finally the problem was produced by an 
empty output of DBpedia Spotlight due to a bad configuration in its side.

Thanks for your help again

Regards

El 03/12/12 19:20, Rupert Westenthaler escribió:
> Hi Reto, Rafa
>
> @Rafa: I do not thing this is related to the spotlight engine
>
> @Reto: Could this be related to the Stanbol Security. Is this already
> active. Andreas Gruber was asking me about the same Exception earlier
> today.
>
> On Mon, Dec 3, 2012 at 7:09 PM, Rafa Haro <rh...@zaizi.com> wrote:
>> //03.12.2012 18:54:25.738 *WARN* [1548445156@qtp-558009892-5]
>> org.apache.felix.http.jetty /enhancer/chain/dbpedia-spotlight
>> (java.lang.RuntimeException: java.security.PrivilegedActionException:
>> java.io.IOException: Stream closed) java.lang.RuntimeException:
>> java.security.PrivilegedActionException: java.io.IOException: Stream
>> closed//
> best
> Rupert
>
> --
> | Rupert Westenthaler             rupert.westenthaler@gmail.com
> | Bodenlehenstraße 11                             ++43-699-11108907
> | A-5500 Bischofshofen

This message should be regarded as confidential. If you have received this email in error please notify the sender and destroy it immediately. Statements of intent shall only become binding when confirmed in hard copy by an authorised signatory.

Zaizi Ltd is registered in England and Wales with the registration number 6440931. The Registered Office is 222 Westbourne Studios, 242 Acklam Road, London W10 5JJ, UK.


Re: DBPedia Spotlight Enhancer is not working

Posted by Rupert Westenthaler <ru...@gmail.com>.
Hi Reto, Rafa

@Rafa: I do not thing this is related to the spotlight engine

@Reto: Could this be related to the Stanbol Security. Is this already
active. Andreas Gruber was asking me about the same Exception earlier
today.

On Mon, Dec 3, 2012 at 7:09 PM, Rafa Haro <rh...@zaizi.com> wrote:
> //03.12.2012 18:54:25.738 *WARN* [1548445156@qtp-558009892-5]
> org.apache.felix.http.jetty /enhancer/chain/dbpedia-spotlight
> (java.lang.RuntimeException: java.security.PrivilegedActionException:
> java.io.IOException: Stream closed) java.lang.RuntimeException:
> java.security.PrivilegedActionException: java.io.IOException: Stream
> closed//

best
Rupert

--
| Rupert Westenthaler             rupert.westenthaler@gmail.com
| Bodenlehenstraße 11                             ++43-699-11108907
| A-5500 Bischofshofen

Re: DBPedia Spotlight Enhancer is not working

Posted by Rafa Haro <rh...@zaizi.com>.
Hi Rupert,


El 03/12/12 18:17, Rupert Westenthaler escribió:
> Hi Rafa,
>
> a fast lookup in the code has shown that SUPPORTED_LANGUAGES is
> hardcoded to "en" at the moment. Making this configureable is not a
> big deal. Even better would be if spotlight would provide a service
> where one can request the supported languages.
>
> I suggest to open a JIRA issue about that. If we go for the "make it
> configureable" option, than I can provide a fix later this week
Sure, I can open it if you want.

Anyway, I have added spanish ("es") directly in the code and I'm not 
getting the error anymore. Unfortunately, it still not working with my 
local DBpedia Sptlight installation. Now, with a spanish text, DBpedia 
Spotlight seems to process it and send the respond to Stanbol as you can 
see in this log:

/dic 03, 2012 6:54:24 PM 
org.dbpedia.spotlight.web.rest.SpotlightInterface announce//
//Información: text: Michael Jeffrey Jordan (Nueva York, 17 de febrero 
de 1963), conocido como Michael Jordan y apodado «Air» («Aire»), «His 
Royal Airness» («Su Majestad del Aire») y «Air Jordan», es un ex jugador 
profesional de baloncesto estadounidense. En la actualidad, es el 
propietario de los Charlotte Bobcats, franquicia de la NBA.2 Está 
considerado por la mayoría de aficionados y especialistas como el mejor 
jugador de baloncesto de la historia.3 Se retiró definitivamente en 
2003, tras haberlo hecho en dos ocasiones anteriores, en 1993 y 1999.//
//Ganó seis anillos con Chicago Bulls, promediando 30,1 puntos por 
partido en toda su carrera, el mayor promedio en la historia de la liga. 
Además, también ganó 10 títulos de máximo anotador, 5 MVP de la 
temporada, 6 MVP de las Finales, nombrado en el mejor quinteto de la NBA 
en diez ocasiones, en el defensivo nueve veces, líder en robos de balón 
durante tres años y un premio al mejor defensor de la temporada.//
//dic 03, 2012 6:54:24 PM 
org.dbpedia.spotlight.web.rest.SpotlightInterface announce//
//Información: text length in chars: 946//
//dic 03, 2012 6:54:24 PM 
org.dbpedia.spotlight.web.rest.SpotlightInterface announce//
//Información: confidence: 0.1//
//dic 03, 2012 6:54:24 PM 
org.dbpedia.spotlight.web.rest.SpotlightInterface announce//
//Información: support: 10//
//dic 03, 2012 6:54:24 PM 
org.dbpedia.spotlight.web.rest.SpotlightInterface announce//
//Información: types: //
//dic 03, 2012 6:54:24 PM 
org.dbpedia.spotlight.web.rest.SpotlightInterface announce//
//Información: sparqlQuery: //
//dic 03, 2012 6:54:24 PM 
org.dbpedia.spotlight.web.rest.SpotlightInterface announce//
//Información: policy: false//
//dic 03, 2012 6:54:24 PM 
org.dbpedia.spotlight.web.rest.SpotlightInterface announce//
//Información: coreferenceResolution: true//
//dic 03, 2012 6:54:24 PM 
org.dbpedia.spotlight.web.rest.SpotlightInterface announce//
//Información: spotter: Default//
//dic 03, 2012 6:54:24 PM 
org.dbpedia.spotlight.web.rest.SpotlightInterface announce//
//Información: disambiguator: Default//
//dic 03, 2012 6:54:24 PM org.dbpedia.spotlight.spot.SpotterWithSelector 
extract//
//Información: Selecting candidates...//
//dic 03, 2012 6:54:24 PM org.dbpedia.spotlight.spot.SpotterWithSelector 
extract//
//Información: Removed 1 (100 percent) spots using spotSelector 
ChainedSelector//
//dic 03, 2012 6:54:25 PM 
org.dbpedia.spotlight.filter.annotations.TypeFilter <init>//
//Información: types are empty: showing all types//
//dic 03, 2012 6:54:25 PM 
org.dbpedia.spotlight.web.rest.SpotlightInterface getXML//
//Información: XML format/

But I'm getting a new error in Stanbol side:

/03.12.2012 18:54:25.701 *INFO* [Thread-63] 
org.apache.stanbol.enhancer.jobmanager.event.impl.EnhancementJobHandler 
content-item: 
<urn:content-item-sha1-4e1e021a361ceee0897f81f6e8d4b909072cd04e>//
//03.12.2012 18:54:25.702 *INFO* [1548445156@qtp-558009892-5] 
org.apache.stanbol.enhancer.jobmanager.event.impl.EventJobManagerImpl 
Finished EnhancementJob for ContentItem 
<urn:content-item-sha1-4e1e021a361ceee0897f81f6e8d4b909072cd04e> after 
7170ms//
//03.12.2012 18:54:25.707 *INFO* [1548445156@qtp-558009892-5] 
org.apache.stanbol.enhancer.jersey.resource.ContentItemResource ... 3ms 
fro parsing Enhancement Reuslts//
//03.12.2012 18:54:25.708 *WARN* [1548445156@qtp-558009892-5] 
org.apache.stanbol.commons.ldpathtemplate.LdRenderer Template 
html/org/apache/stanbol/enhancer/jersey/resource/ContentItemResource/ajax/contentitem_es_ES.ftl 
not known//
//03.12.2012 18:54:25.708 *WARN* [1548445156@qtp-558009892-5] 
org.apache.stanbol.commons.ldpathtemplate.LdRenderer Template 
html/org/apache/stanbol/enhancer/jersey/resource/ContentItemResource/ajax/contentitem_es.ftl 
not known//
//03.12.2012 18:54:25.710 *WARN* [1548445156@qtp-558009892-5] 
org.apache.stanbol.commons.ldpathtemplate.LdRenderer Template 
imports/contentitem_es_ES.ftl not known//
//03.12.2012 18:54:25.710 *WARN* [1548445156@qtp-558009892-5] 
org.apache.stanbol.commons.ldpathtemplate.LdRenderer Template 
imports/contentitem_es.ftl not known//
//03.12.2012 18:54:25.714 *WARN* [1548445156@qtp-558009892-5] 
org.apache.stanbol.commons.ldpathtemplate.LdRenderer Template 
imports/entities_es_ES.ftl not known//
//03.12.2012 18:54:25.715 *WARN* [1548445156@qtp-558009892-5] 
org.apache.stanbol.commons.ldpathtemplate.LdRenderer Template 
imports/entities_es.ftl not known//
//03.12.2012 18:54:25.718 *WARN* [1548445156@qtp-558009892-5] 
org.apache.stanbol.commons.ldpathtemplate.LdRenderer Template 
imports/executionmetadata_es_ES.ftl not known//
//03.12.2012 18:54:25.718 *WARN* [1548445156@qtp-558009892-5] 
org.apache.stanbol.commons.ldpathtemplate.LdRenderer Template 
imports/executionmetadata_es.ftl not known//
//03.12.2012 18:54:25.738 *WARN* [1548445156@qtp-558009892-5] 
org.apache.felix.http.jetty /enhancer/chain/dbpedia-spotlight 
(java.lang.RuntimeException: java.security.PrivilegedActionException: 
java.io.IOException: Stream closed) java.lang.RuntimeException: 
java.security.PrivilegedActionException: java.io.IOException: Stream 
closed//
//        at 
org.apache.stanbol.commons.security.auth.AuthenticatingFilter.doFilter(AuthenticatingFilter.java:176)//
//        at 
org.apache.felix.http.base.internal.handler.FilterHandler.doHandle(FilterHandler.java:88)//
//        at 
org.apache.felix.http.base.internal.handler.FilterHandler.handle(FilterHandler.java:76)//
//        at 
org.apache.felix.http.base.internal.dispatch.InvocationFilterChain.doFilter(InvocationFilterChain.java:47)//
//        at 
org.apache.felix.http.base.internal.dispatch.HttpFilterChain.doFilter(HttpFilterChain.java:33)//
//        at 
org.apache.felix.http.base.internal.dispatch.FilterPipeline.dispatch(FilterPipeline.java:48)//
//        at 
org.apache.felix.http.base.internal.dispatch.Dispatcher.dispatch(Dispatcher.java:39)//
//        at 
org.apache.felix.http.base.internal.DispatcherServlet.service(DispatcherServlet.java:67)//
//        at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)//
//        at 
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)//
//        at 
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:390)//
//        at 
org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)//
//        at 
org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)//
//        at 
org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)//
//        at org.mortbay.jetty.Server.handle(Server.java:326)//
//        at 
org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)//
//        at 
org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:943)//
//        at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:756)//
//        at 
org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218)//
//        at 
org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)//
//        at 
org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410)//
//        at 
org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)//
//Caused by: java.security.PrivilegedActionException: 
java.io.IOException: Stream closed//
//        at java.security.AccessController.doPrivileged(Native Method)//
//        at javax.security.auth.Subject.doAsPrivileged(Subject.java:536)//
//        at 
org.apache.stanbol.commons.security.auth.AuthenticatingFilter.doFilter(AuthenticatingFilter.java:159)//
//        ... 21 more//
//Caused by: java.io.IOException: Stream closed//
//        at sun.nio.cs.StreamEncoder.ensureOpen(StreamEncoder.java:45)//
//        at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:140)//
//        at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:229)//
//        at 
org.apache.stanbol.commons.viewable.mbw.ViewableWriter.writeTo(ViewableWriter.java:67)//
//        at 
org.apache.stanbol.commons.viewable.mbw.ViewableWriter.writeTo(ViewableWriter.java:38)//
//        at 
com.sun.jersey.spi.container.ContainerResponse.write(ContainerResponse.java:306)//
//        at 
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1448)//
//        at 
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1360)//
//        at 
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1350)//
//        at 
com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:416)//
//        at 
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:538)/

I'm not sure if this can be produced by an empty output of DBPedia 
Spotlight.

Regards
>
> best
> Rupert
>
> On Mon, Dec 3, 2012 at 4:33 PM, Iavor Jelev
> <ia...@babelmonkeys.com> wrote:
>> Hi Rafa,
>>
>> yes, it should. For Spanish - add (or change to) "es". For further
>> languages, please refer to:
>>
>> http://stanbol.apache.org/docs/trunk/components/enhancer/engines/langidengine.html
>>
>> cheers,
>> Iavor
>>
>> Am 03.12.2012 16:28, schrieb Rafa Haro:
>>> Hi Iavor,
>>>
>>> thanks for your quick response. Until have it configurable, to get by
>>> now, would it work just adding new languages to this parameter?
>>>
>>> Thanks. Regards
>>>
>>> El 03/12/12 15:58, Iavor Jelev escribió:
>>>> Hi Rafa,
>>>>
>>>> you are correct, that's the cause. At the time we contributed it, we
>>>> aggreed on english. The parameter can be found in [path to
>>>> engines]/dbpspotlight/Constants.java
>>>>
>>>> The parameter is called SUPPORTED_LANGUAGES.
>>>>
>>>> I think it is time we make that configurable.
>>>>
>>>> best,
>>>> Iavor
>>>>
>>>> Am 03.12.2012 14:37, schrieb Rafa Haro:
>>>>> Hi again,
>>>>>
>>>>> In the post about DBpedia Spotlight and Apache Stanbol Integration by
>>>>> Iavor Jelev [1] you can read exactly the following:
>>>>>
>>>>> */$chainURL/dbpspotlight/*/
>>>>> //This chain replicates the functionality of dbpspotlightannotate, by
>>>>> chaining dbpspotlightspot and dbpspotlightdisambiguate. Please note that
>>>>> langidis run first, and only english texts are processed. In the near
>>>>> future, DBpedia Spotlight will support multiple languages and this
>>>>> constraint will be adapted accordingly./
>>>>>
>>>>> Is this maybe a hard-coded restriction?
>>>>>
>>>>> Regards
>>>>>
>>>>> [1]
>>>>> http://blog.iks-project.eu/dbpedia-spotlight-integration-in-apache-stanbol-2/
>>>>>
>>>>>
>>>>>
>>>>> El 03/12/12 09:39, Rafa Haro escribió:
>>>>>> Hi Rupert,
>>>>>>
>>>>>> As always, thanks for your help. Inspecting the logs, part of the
>>>>>> mystery has clarified. Basically, the problem is the language. I'm
>>>>>> trying to test DBPedia Spotlight enhancer with Spanish texts. So, I
>>>>>> did a request to the Stanbol Dev Server with a Spanish text and got
>>>>>> the same result. Then I configured again my local Stanbol to work with
>>>>>> a local installation of DBPedia Spotlight, try again with a Spanish
>>>>>> text and this time I can read the following messages in the log file:
>>>>>> /
>>>>>> //[Thread-114]
>>>>>> org.apache.stanbol.enhancer.engines.langdetect.LanguageDetectionEnhancementEngine
>>>>>>
>>>>>> language identified: [es:0.999996063192582]//
>>>>>> //03.12.2012 08:52:55.386 *INFO* [Thread-116]
>>>>>> org.apache.stanbol.enhancer.engines.dbpspotlight.utils.SpotlightEngineUtils
>>>>>>
>>>>>> DBpedia Spotlight can not process ContentItem
>>>>>> <urn:content-item-sha1-4e1e021a361ceee0897f81f6e8d4b909072cd04e>
>>>>>> because language es is not supported (supported: [en])/
>>>>>>
>>>>>> So far, I haven't been able to find anything to change supported
>>>>>> languages for the enhancer. I suppose that it should be possible to do
>>>>>> that, am I wrong??
>>>>>>
>>>>>> Thanks. Regards
>>>>>>
>>>>>> El 01/12/12 15:19, Rupert Westenthaler escribió:
>>>>>>> On Fri, Nov 30, 2012 at 2:14 PM, Rafa Haro<rh...@zaizi.com>  wrote:
>>>>>>>> Hi all,
>>>>>>>>
>>>>>>>> I was trying to test the DBPedia Spotlight enhancer with a local
>>>>>>>> installation of DBPedia Spotlight in an out-of-the-box Stanbol
>>>>>>>> from the
>>>>>>>> repository. So, I changed the URL of the service in
>>>>>>>> dbpspotlightannotate
>>>>>>>> engine to my point to my local service endpoint. When I tested it,
>>>>>>>> the
>>>>>>>> enhancement chain always stopped at language detection engine. I
>>>>>>>> thought
>>>>>>>> that maybe there was any error with my local installation, but then
>>>>>>>> I tried
>>>>>>>> again with the default URL endpoint
>>>>>>>> (http://spotlight.dbpedia.org/rest/annotate) and got the same result.
>>>>>>> I have never tried to change the configuration of the service URL so
>>>>>>> this might be a Bug. Is your Spotlight service public accessible. If
>>>>>>> so I could try to replicate this. If you do not want send the URL on a
>>>>>>> public mailing list feel free to send it directly to me.
>>>>>>>
>>>>>>>> The
>>>>>>>> only clue I have so far is the following message in the console
>>>>>>>> where I run
>>>>>>>> Stanbol:
>>>>>>>> /
>>>>>>>> //A servlet request, to the URI
>>>>>>>> http://192.168.1.35:8080/enhancer/chain/dbpedia-spotlight, contains
>>>>>>>> form
>>>>>>>> parameters in the request body but the request body has been
>>>>>>>> consumed by the
>>>>>>>> servlet or a servlet filter accessing the request parameters. Only
>>>>>>>> resource
>>>>>>>> methods using @FormParam will work as expected. Resource methods
>>>>>>>> consuming
>>>>>>>> the request body by other means will not work as expected./
>>>>>>>>
>>>>>>> This message is triggered by any Request to Stanbol when the
>>>>>>> "httpqueryheaders" module is active. It can not be the cause for your
>>>>>>> problem.
>>>>>>>
>>>>>>> Are there any loggings in the Stanbol log file?
>>>>>>> What is the exact Chain configuration you are using?
>>>>>>>
>>>>>>> On the Stanbol Dev Server [1] (nightly build) it seams to work.
>>>>>>>
>>>>>>> best
>>>>>>> Rupert
>>>>>>>
>>>>>>> [1]http://dev.iks-project.eu:8081/enhancer/chain/dbpedia-spotlight
>>>>>>>
>>>>>>>> Does anyone know what can be happening??
>>>>>>>>
>>>>>>>> Regards
>>>>>>>>
>>>>>>>> This message should be regarded as confidential. If you have
>>>>>>>> received this
>>>>>>>> email in error please notify the sender and destroy it immediately.
>>>>>>>> Statements of intent shall only become binding when confirmed in
>>>>>>>> hard copy
>>>>>>>> by an authorised signatory.
>>>>>>>>
>>>>>>>> Zaizi Ltd is registered in England and Wales with the registration
>>>>>>>> number
>>>>>>>> 6440931. The Registered Office is 222 Westbourne Studios, 242 Acklam
>>>>>>>> Road,
>>>>>>>> London W10 5JJ, UK.
>>>>>>> --
>>>>>>> | Rupert Westenthalerrupert.westenthaler@gmail.com
>>>>>>> | Bodenlehenstraße 11                             ++43-699-11108907
>>>>>>> | A-5500 Bischofshofen
>>>>> This message should be regarded as confidential. If you have received
>>>>> this email in error please notify the sender and destroy it immediately.
>>>>> Statements of intent shall only become binding when confirmed in hard
>>>>> copy by an authorised signatory.
>>>>>
>>>>> Zaizi Ltd is registered in England and Wales with the registration
>>>>> number 6440931. The Registered Office is 222 Westbourne Studios, 242
>>>>> Acklam Road, London W10 5JJ, UK.
>>>>>
>>> This message should be regarded as confidential. If you have received
>>> this email in error please notify the sender and destroy it immediately.
>>> Statements of intent shall only become binding when confirmed in hard
>>> copy by an authorised signatory.
>>>
>>> Zaizi Ltd is registered in England and Wales with the registration
>>> number 6440931. The Registered Office is 222 Westbourne Studios, 242
>>> Acklam Road, London W10 5JJ, UK.
>>>
>
>


This message should be regarded as confidential. If you have received this email in error please notify the sender and destroy it immediately. Statements of intent shall only become binding when confirmed in hard copy by an authorised signatory.

Zaizi Ltd is registered in England and Wales with the registration number 6440931. The Registered Office is 222 Westbourne Studios, 242 Acklam Road, London W10 5JJ, UK.

Re: DBPedia Spotlight Enhancer is not working

Posted by Rupert Westenthaler <ru...@gmail.com>.
Hi Rafa,

a fast lookup in the code has shown that SUPPORTED_LANGUAGES is
hardcoded to "en" at the moment. Making this configureable is not a
big deal. Even better would be if spotlight would provide a service
where one can request the supported languages.

I suggest to open a JIRA issue about that. If we go for the "make it
configureable" option, than I can provide a fix later this week

best
Rupert

On Mon, Dec 3, 2012 at 4:33 PM, Iavor Jelev
<ia...@babelmonkeys.com> wrote:
> Hi Rafa,
>
> yes, it should. For Spanish - add (or change to) "es". For further
> languages, please refer to:
>
> http://stanbol.apache.org/docs/trunk/components/enhancer/engines/langidengine.html
>
> cheers,
> Iavor
>
> Am 03.12.2012 16:28, schrieb Rafa Haro:
>> Hi Iavor,
>>
>> thanks for your quick response. Until have it configurable, to get by
>> now, would it work just adding new languages to this parameter?
>>
>> Thanks. Regards
>>
>> El 03/12/12 15:58, Iavor Jelev escribió:
>>> Hi Rafa,
>>>
>>> you are correct, that's the cause. At the time we contributed it, we
>>> aggreed on english. The parameter can be found in [path to
>>> engines]/dbpspotlight/Constants.java
>>>
>>> The parameter is called SUPPORTED_LANGUAGES.
>>>
>>> I think it is time we make that configurable.
>>>
>>> best,
>>> Iavor
>>>
>>> Am 03.12.2012 14:37, schrieb Rafa Haro:
>>>> Hi again,
>>>>
>>>> In the post about DBpedia Spotlight and Apache Stanbol Integration by
>>>> Iavor Jelev [1] you can read exactly the following:
>>>>
>>>> */$chainURL/dbpspotlight/*/
>>>> //This chain replicates the functionality of dbpspotlightannotate, by
>>>> chaining dbpspotlightspot and dbpspotlightdisambiguate. Please note that
>>>> langidis run first, and only english texts are processed. In the near
>>>> future, DBpedia Spotlight will support multiple languages and this
>>>> constraint will be adapted accordingly./
>>>>
>>>> Is this maybe a hard-coded restriction?
>>>>
>>>> Regards
>>>>
>>>> [1]
>>>> http://blog.iks-project.eu/dbpedia-spotlight-integration-in-apache-stanbol-2/
>>>>
>>>>
>>>>
>>>> El 03/12/12 09:39, Rafa Haro escribió:
>>>>> Hi Rupert,
>>>>>
>>>>> As always, thanks for your help. Inspecting the logs, part of the
>>>>> mystery has clarified. Basically, the problem is the language. I'm
>>>>> trying to test DBPedia Spotlight enhancer with Spanish texts. So, I
>>>>> did a request to the Stanbol Dev Server with a Spanish text and got
>>>>> the same result. Then I configured again my local Stanbol to work with
>>>>> a local installation of DBPedia Spotlight, try again with a Spanish
>>>>> text and this time I can read the following messages in the log file:
>>>>> /
>>>>> //[Thread-114]
>>>>> org.apache.stanbol.enhancer.engines.langdetect.LanguageDetectionEnhancementEngine
>>>>>
>>>>> language identified: [es:0.999996063192582]//
>>>>> //03.12.2012 08:52:55.386 *INFO* [Thread-116]
>>>>> org.apache.stanbol.enhancer.engines.dbpspotlight.utils.SpotlightEngineUtils
>>>>>
>>>>> DBpedia Spotlight can not process ContentItem
>>>>> <urn:content-item-sha1-4e1e021a361ceee0897f81f6e8d4b909072cd04e>
>>>>> because language es is not supported (supported: [en])/
>>>>>
>>>>> So far, I haven't been able to find anything to change supported
>>>>> languages for the enhancer. I suppose that it should be possible to do
>>>>> that, am I wrong??
>>>>>
>>>>> Thanks. Regards
>>>>>
>>>>> El 01/12/12 15:19, Rupert Westenthaler escribió:
>>>>>> On Fri, Nov 30, 2012 at 2:14 PM, Rafa Haro<rh...@zaizi.com>  wrote:
>>>>>>> Hi all,
>>>>>>>
>>>>>>> I was trying to test the DBPedia Spotlight enhancer with a local
>>>>>>> installation of DBPedia Spotlight in an out-of-the-box Stanbol
>>>>>>> from the
>>>>>>> repository. So, I changed the URL of the service in
>>>>>>> dbpspotlightannotate
>>>>>>> engine to my point to my local service endpoint. When I tested it,
>>>>>>> the
>>>>>>> enhancement chain always stopped at language detection engine. I
>>>>>>> thought
>>>>>>> that maybe there was any error with my local installation, but then
>>>>>>> I tried
>>>>>>> again with the default URL endpoint
>>>>>>> (http://spotlight.dbpedia.org/rest/annotate) and got the same result.
>>>>>> I have never tried to change the configuration of the service URL so
>>>>>> this might be a Bug. Is your Spotlight service public accessible. If
>>>>>> so I could try to replicate this. If you do not want send the URL on a
>>>>>> public mailing list feel free to send it directly to me.
>>>>>>
>>>>>>> The
>>>>>>> only clue I have so far is the following message in the console
>>>>>>> where I run
>>>>>>> Stanbol:
>>>>>>> /
>>>>>>> //A servlet request, to the URI
>>>>>>> http://192.168.1.35:8080/enhancer/chain/dbpedia-spotlight, contains
>>>>>>> form
>>>>>>> parameters in the request body but the request body has been
>>>>>>> consumed by the
>>>>>>> servlet or a servlet filter accessing the request parameters. Only
>>>>>>> resource
>>>>>>> methods using @FormParam will work as expected. Resource methods
>>>>>>> consuming
>>>>>>> the request body by other means will not work as expected./
>>>>>>>
>>>>>> This message is triggered by any Request to Stanbol when the
>>>>>> "httpqueryheaders" module is active. It can not be the cause for your
>>>>>> problem.
>>>>>>
>>>>>> Are there any loggings in the Stanbol log file?
>>>>>> What is the exact Chain configuration you are using?
>>>>>>
>>>>>> On the Stanbol Dev Server [1] (nightly build) it seams to work.
>>>>>>
>>>>>> best
>>>>>> Rupert
>>>>>>
>>>>>> [1]http://dev.iks-project.eu:8081/enhancer/chain/dbpedia-spotlight
>>>>>>
>>>>>>> Does anyone know what can be happening??
>>>>>>>
>>>>>>> Regards
>>>>>>>
>>>>>>> This message should be regarded as confidential. If you have
>>>>>>> received this
>>>>>>> email in error please notify the sender and destroy it immediately.
>>>>>>> Statements of intent shall only become binding when confirmed in
>>>>>>> hard copy
>>>>>>> by an authorised signatory.
>>>>>>>
>>>>>>> Zaizi Ltd is registered in England and Wales with the registration
>>>>>>> number
>>>>>>> 6440931. The Registered Office is 222 Westbourne Studios, 242 Acklam
>>>>>>> Road,
>>>>>>> London W10 5JJ, UK.
>>>>>> --
>>>>>> | Rupert Westenthalerrupert.westenthaler@gmail.com
>>>>>> | Bodenlehenstraße 11                             ++43-699-11108907
>>>>>> | A-5500 Bischofshofen
>>>>
>>>> This message should be regarded as confidential. If you have received
>>>> this email in error please notify the sender and destroy it immediately.
>>>> Statements of intent shall only become binding when confirmed in hard
>>>> copy by an authorised signatory.
>>>>
>>>> Zaizi Ltd is registered in England and Wales with the registration
>>>> number 6440931. The Registered Office is 222 Westbourne Studios, 242
>>>> Acklam Road, London W10 5JJ, UK.
>>>>
>>
>> This message should be regarded as confidential. If you have received
>> this email in error please notify the sender and destroy it immediately.
>> Statements of intent shall only become binding when confirmed in hard
>> copy by an authorised signatory.
>>
>> Zaizi Ltd is registered in England and Wales with the registration
>> number 6440931. The Registered Office is 222 Westbourne Studios, 242
>> Acklam Road, London W10 5JJ, UK.
>>
>



-- 
| Rupert Westenthaler             rupert.westenthaler@gmail.com
| Bodenlehenstraße 11                             ++43-699-11108907
| A-5500 Bischofshofen

Re: DBPedia Spotlight Enhancer is not working

Posted by Iavor Jelev <ia...@babelmonkeys.com>.
Hi Rafa,

yes, it should. For Spanish - add (or change to) "es". For further
languages, please refer to:

http://stanbol.apache.org/docs/trunk/components/enhancer/engines/langidengine.html

cheers,
Iavor

Am 03.12.2012 16:28, schrieb Rafa Haro:
> Hi Iavor,
> 
> thanks for your quick response. Until have it configurable, to get by
> now, would it work just adding new languages to this parameter?
> 
> Thanks. Regards
> 
> El 03/12/12 15:58, Iavor Jelev escribió:
>> Hi Rafa,
>>
>> you are correct, that's the cause. At the time we contributed it, we
>> aggreed on english. The parameter can be found in [path to
>> engines]/dbpspotlight/Constants.java
>>
>> The parameter is called SUPPORTED_LANGUAGES.
>>
>> I think it is time we make that configurable.
>>
>> best,
>> Iavor
>>
>> Am 03.12.2012 14:37, schrieb Rafa Haro:
>>> Hi again,
>>>
>>> In the post about DBpedia Spotlight and Apache Stanbol Integration by
>>> Iavor Jelev [1] you can read exactly the following:
>>>
>>> */$chainURL/dbpspotlight/*/
>>> //This chain replicates the functionality of dbpspotlightannotate, by
>>> chaining dbpspotlightspot and dbpspotlightdisambiguate. Please note that
>>> langidis run first, and only english texts are processed. In the near
>>> future, DBpedia Spotlight will support multiple languages and this
>>> constraint will be adapted accordingly./
>>>
>>> Is this maybe a hard-coded restriction?
>>>
>>> Regards
>>>
>>> [1]
>>> http://blog.iks-project.eu/dbpedia-spotlight-integration-in-apache-stanbol-2/
>>>
>>>
>>>
>>> El 03/12/12 09:39, Rafa Haro escribió:
>>>> Hi Rupert,
>>>>
>>>> As always, thanks for your help. Inspecting the logs, part of the
>>>> mystery has clarified. Basically, the problem is the language. I'm
>>>> trying to test DBPedia Spotlight enhancer with Spanish texts. So, I
>>>> did a request to the Stanbol Dev Server with a Spanish text and got
>>>> the same result. Then I configured again my local Stanbol to work with
>>>> a local installation of DBPedia Spotlight, try again with a Spanish
>>>> text and this time I can read the following messages in the log file:
>>>> /
>>>> //[Thread-114]
>>>> org.apache.stanbol.enhancer.engines.langdetect.LanguageDetectionEnhancementEngine
>>>>
>>>> language identified: [es:0.999996063192582]//
>>>> //03.12.2012 08:52:55.386 *INFO* [Thread-116]
>>>> org.apache.stanbol.enhancer.engines.dbpspotlight.utils.SpotlightEngineUtils
>>>>
>>>> DBpedia Spotlight can not process ContentItem
>>>> <urn:content-item-sha1-4e1e021a361ceee0897f81f6e8d4b909072cd04e>
>>>> because language es is not supported (supported: [en])/
>>>>
>>>> So far, I haven't been able to find anything to change supported
>>>> languages for the enhancer. I suppose that it should be possible to do
>>>> that, am I wrong??
>>>>
>>>> Thanks. Regards
>>>>
>>>> El 01/12/12 15:19, Rupert Westenthaler escribió:
>>>>> On Fri, Nov 30, 2012 at 2:14 PM, Rafa Haro<rh...@zaizi.com>  wrote:
>>>>>> Hi all,
>>>>>>
>>>>>> I was trying to test the DBPedia Spotlight enhancer with a local
>>>>>> installation of DBPedia Spotlight in an out-of-the-box Stanbol
>>>>>> from the
>>>>>> repository. So, I changed the URL of the service in
>>>>>> dbpspotlightannotate
>>>>>> engine to my point to my local service endpoint. When I tested it,
>>>>>> the
>>>>>> enhancement chain always stopped at language detection engine. I
>>>>>> thought
>>>>>> that maybe there was any error with my local installation, but then
>>>>>> I tried
>>>>>> again with the default URL endpoint
>>>>>> (http://spotlight.dbpedia.org/rest/annotate) and got the same result.
>>>>> I have never tried to change the configuration of the service URL so
>>>>> this might be a Bug. Is your Spotlight service public accessible. If
>>>>> so I could try to replicate this. If you do not want send the URL on a
>>>>> public mailing list feel free to send it directly to me.
>>>>>
>>>>>> The
>>>>>> only clue I have so far is the following message in the console
>>>>>> where I run
>>>>>> Stanbol:
>>>>>> /
>>>>>> //A servlet request, to the URI
>>>>>> http://192.168.1.35:8080/enhancer/chain/dbpedia-spotlight, contains
>>>>>> form
>>>>>> parameters in the request body but the request body has been
>>>>>> consumed by the
>>>>>> servlet or a servlet filter accessing the request parameters. Only
>>>>>> resource
>>>>>> methods using @FormParam will work as expected. Resource methods
>>>>>> consuming
>>>>>> the request body by other means will not work as expected./
>>>>>>
>>>>> This message is triggered by any Request to Stanbol when the
>>>>> "httpqueryheaders" module is active. It can not be the cause for your
>>>>> problem.
>>>>>
>>>>> Are there any loggings in the Stanbol log file?
>>>>> What is the exact Chain configuration you are using?
>>>>>
>>>>> On the Stanbol Dev Server [1] (nightly build) it seams to work.
>>>>>
>>>>> best
>>>>> Rupert
>>>>>
>>>>> [1]http://dev.iks-project.eu:8081/enhancer/chain/dbpedia-spotlight
>>>>>
>>>>>> Does anyone know what can be happening??
>>>>>>
>>>>>> Regards
>>>>>>
>>>>>> This message should be regarded as confidential. If you have
>>>>>> received this
>>>>>> email in error please notify the sender and destroy it immediately.
>>>>>> Statements of intent shall only become binding when confirmed in
>>>>>> hard copy
>>>>>> by an authorised signatory.
>>>>>>
>>>>>> Zaizi Ltd is registered in England and Wales with the registration
>>>>>> number
>>>>>> 6440931. The Registered Office is 222 Westbourne Studios, 242 Acklam
>>>>>> Road,
>>>>>> London W10 5JJ, UK.
>>>>> -- 
>>>>> | Rupert Westenthalerrupert.westenthaler@gmail.com
>>>>> | Bodenlehenstraße 11                             ++43-699-11108907
>>>>> | A-5500 Bischofshofen
>>>
>>> This message should be regarded as confidential. If you have received
>>> this email in error please notify the sender and destroy it immediately.
>>> Statements of intent shall only become binding when confirmed in hard
>>> copy by an authorised signatory.
>>>
>>> Zaizi Ltd is registered in England and Wales with the registration
>>> number 6440931. The Registered Office is 222 Westbourne Studios, 242
>>> Acklam Road, London W10 5JJ, UK.
>>>
> 
> This message should be regarded as confidential. If you have received
> this email in error please notify the sender and destroy it immediately.
> Statements of intent shall only become binding when confirmed in hard
> copy by an authorised signatory.
> 
> Zaizi Ltd is registered in England and Wales with the registration
> number 6440931. The Registered Office is 222 Westbourne Studios, 242
> Acklam Road, London W10 5JJ, UK.
> 


Re: DBPedia Spotlight Enhancer is not working

Posted by Rafa Haro <rh...@zaizi.com>.
Hi Iavor,

thanks for your quick response. Until have it configurable, to get by 
now, would it work just adding new languages to this parameter?

Thanks. Regards

El 03/12/12 15:58, Iavor Jelev escribió:
> Hi Rafa,
>
> you are correct, that's the cause. At the time we contributed it, we
> aggreed on english. The parameter can be found in [path to
> engines]/dbpspotlight/Constants.java
>
> The parameter is called SUPPORTED_LANGUAGES.
>
> I think it is time we make that configurable.
>
> best,
> Iavor
>
> Am 03.12.2012 14:37, schrieb Rafa Haro:
>> Hi again,
>>
>> In the post about DBpedia Spotlight and Apache Stanbol Integration by
>> Iavor Jelev [1] you can read exactly the following:
>>
>> */$chainURL/dbpspotlight/*/
>> //This chain replicates the functionality of dbpspotlightannotate, by
>> chaining dbpspotlightspot and dbpspotlightdisambiguate. Please note that
>> langidis run first, and only english texts are processed. In the near
>> future, DBpedia Spotlight will support multiple languages and this
>> constraint will be adapted accordingly./
>>
>> Is this maybe a hard-coded restriction?
>>
>> Regards
>>
>> [1]
>> http://blog.iks-project.eu/dbpedia-spotlight-integration-in-apache-stanbol-2/
>>
>>
>> El 03/12/12 09:39, Rafa Haro escribió:
>>> Hi Rupert,
>>>
>>> As always, thanks for your help. Inspecting the logs, part of the
>>> mystery has clarified. Basically, the problem is the language. I'm
>>> trying to test DBPedia Spotlight enhancer with Spanish texts. So, I
>>> did a request to the Stanbol Dev Server with a Spanish text and got
>>> the same result. Then I configured again my local Stanbol to work with
>>> a local installation of DBPedia Spotlight, try again with a Spanish
>>> text and this time I can read the following messages in the log file:
>>> /
>>> //[Thread-114]
>>> org.apache.stanbol.enhancer.engines.langdetect.LanguageDetectionEnhancementEngine
>>> language identified: [es:0.999996063192582]//
>>> //03.12.2012 08:52:55.386 *INFO* [Thread-116]
>>> org.apache.stanbol.enhancer.engines.dbpspotlight.utils.SpotlightEngineUtils
>>> DBpedia Spotlight can not process ContentItem
>>> <urn:content-item-sha1-4e1e021a361ceee0897f81f6e8d4b909072cd04e>
>>> because language es is not supported (supported: [en])/
>>>
>>> So far, I haven't been able to find anything to change supported
>>> languages for the enhancer. I suppose that it should be possible to do
>>> that, am I wrong??
>>>
>>> Thanks. Regards
>>>
>>> El 01/12/12 15:19, Rupert Westenthaler escribió:
>>>> On Fri, Nov 30, 2012 at 2:14 PM, Rafa Haro<rh...@zaizi.com>  wrote:
>>>>> Hi all,
>>>>>
>>>>> I was trying to test the DBPedia Spotlight enhancer with a local
>>>>> installation of DBPedia Spotlight in an out-of-the-box Stanbol from the
>>>>> repository. So, I changed the URL of the service in
>>>>> dbpspotlightannotate
>>>>> engine to my point to my local service endpoint. When I tested it, the
>>>>> enhancement chain always stopped at language detection engine. I
>>>>> thought
>>>>> that maybe there was any error with my local installation, but then
>>>>> I tried
>>>>> again with the default URL endpoint
>>>>> (http://spotlight.dbpedia.org/rest/annotate) and got the same result.
>>>> I have never tried to change the configuration of the service URL so
>>>> this might be a Bug. Is your Spotlight service public accessible. If
>>>> so I could try to replicate this. If you do not want send the URL on a
>>>> public mailing list feel free to send it directly to me.
>>>>
>>>>> The
>>>>> only clue I have so far is the following message in the console
>>>>> where I run
>>>>> Stanbol:
>>>>> /
>>>>> //A servlet request, to the URI
>>>>> http://192.168.1.35:8080/enhancer/chain/dbpedia-spotlight, contains
>>>>> form
>>>>> parameters in the request body but the request body has been
>>>>> consumed by the
>>>>> servlet or a servlet filter accessing the request parameters. Only
>>>>> resource
>>>>> methods using @FormParam will work as expected. Resource methods
>>>>> consuming
>>>>> the request body by other means will not work as expected./
>>>>>
>>>> This message is triggered by any Request to Stanbol when the
>>>> "httpqueryheaders" module is active. It can not be the cause for your
>>>> problem.
>>>>
>>>> Are there any loggings in the Stanbol log file?
>>>> What is the exact Chain configuration you are using?
>>>>
>>>> On the Stanbol Dev Server [1] (nightly build) it seams to work.
>>>>
>>>> best
>>>> Rupert
>>>>
>>>> [1]http://dev.iks-project.eu:8081/enhancer/chain/dbpedia-spotlight
>>>>
>>>>> Does anyone know what can be happening??
>>>>>
>>>>> Regards
>>>>>
>>>>> This message should be regarded as confidential. If you have
>>>>> received this
>>>>> email in error please notify the sender and destroy it immediately.
>>>>> Statements of intent shall only become binding when confirmed in
>>>>> hard copy
>>>>> by an authorised signatory.
>>>>>
>>>>> Zaizi Ltd is registered in England and Wales with the registration
>>>>> number
>>>>> 6440931. The Registered Office is 222 Westbourne Studios, 242 Acklam
>>>>> Road,
>>>>> London W10 5JJ, UK.
>>>> -- 
>>>> | Rupert Westenthalerrupert.westenthaler@gmail.com
>>>> | Bodenlehenstraße 11                             ++43-699-11108907
>>>> | A-5500 Bischofshofen
>>
>> This message should be regarded as confidential. If you have received
>> this email in error please notify the sender and destroy it immediately.
>> Statements of intent shall only become binding when confirmed in hard
>> copy by an authorised signatory.
>>
>> Zaizi Ltd is registered in England and Wales with the registration
>> number 6440931. The Registered Office is 222 Westbourne Studios, 242
>> Acklam Road, London W10 5JJ, UK.
>>

This message should be regarded as confidential. If you have received this email in error please notify the sender and destroy it immediately. Statements of intent shall only become binding when confirmed in hard copy by an authorised signatory.

Zaizi Ltd is registered in England and Wales with the registration number 6440931. The Registered Office is 222 Westbourne Studios, 242 Acklam Road, London W10 5JJ, UK.


Re: DBPedia Spotlight Enhancer is not working

Posted by Iavor Jelev <ia...@babelmonkeys.com>.
Hi Rafa,

you are correct, that's the cause. At the time we contributed it, we
aggreed on english. The parameter can be found in [path to
engines]/dbpspotlight/Constants.java

The parameter is called SUPPORTED_LANGUAGES.

I think it is time we make that configurable.

best,
Iavor

Am 03.12.2012 14:37, schrieb Rafa Haro:
> Hi again,
> 
> In the post about DBpedia Spotlight and Apache Stanbol Integration by
> Iavor Jelev [1] you can read exactly the following:
> 
> */$chainURL/dbpspotlight/*/
> //This chain replicates the functionality of dbpspotlightannotate, by
> chaining dbpspotlightspot and dbpspotlightdisambiguate. Please note that
> langidis run first, and only english texts are processed. In the near
> future, DBpedia Spotlight will support multiple languages and this
> constraint will be adapted accordingly./
> 
> Is this maybe a hard-coded restriction?
> 
> Regards
> 
> [1]
> http://blog.iks-project.eu/dbpedia-spotlight-integration-in-apache-stanbol-2/
> 
> 
> El 03/12/12 09:39, Rafa Haro escribió:
>> Hi Rupert,
>>
>> As always, thanks for your help. Inspecting the logs, part of the
>> mystery has clarified. Basically, the problem is the language. I'm
>> trying to test DBPedia Spotlight enhancer with Spanish texts. So, I
>> did a request to the Stanbol Dev Server with a Spanish text and got
>> the same result. Then I configured again my local Stanbol to work with
>> a local installation of DBPedia Spotlight, try again with a Spanish
>> text and this time I can read the following messages in the log file:
>> /
>> //[Thread-114]
>> org.apache.stanbol.enhancer.engines.langdetect.LanguageDetectionEnhancementEngine
>> language identified: [es:0.999996063192582]//
>> //03.12.2012 08:52:55.386 *INFO* [Thread-116]
>> org.apache.stanbol.enhancer.engines.dbpspotlight.utils.SpotlightEngineUtils
>> DBpedia Spotlight can not process ContentItem
>> <urn:content-item-sha1-4e1e021a361ceee0897f81f6e8d4b909072cd04e>
>> because language es is not supported (supported: [en])/
>>
>> So far, I haven't been able to find anything to change supported
>> languages for the enhancer. I suppose that it should be possible to do
>> that, am I wrong??
>>
>> Thanks. Regards
>>
>> El 01/12/12 15:19, Rupert Westenthaler escribió:
>>> On Fri, Nov 30, 2012 at 2:14 PM, Rafa Haro<rh...@zaizi.com>  wrote:
>>>> Hi all,
>>>>
>>>> I was trying to test the DBPedia Spotlight enhancer with a local
>>>> installation of DBPedia Spotlight in an out-of-the-box Stanbol from the
>>>> repository. So, I changed the URL of the service in
>>>> dbpspotlightannotate
>>>> engine to my point to my local service endpoint. When I tested it, the
>>>> enhancement chain always stopped at language detection engine. I
>>>> thought
>>>> that maybe there was any error with my local installation, but then
>>>> I tried
>>>> again with the default URL endpoint
>>>> (http://spotlight.dbpedia.org/rest/annotate) and got the same result.
>>> I have never tried to change the configuration of the service URL so
>>> this might be a Bug. Is your Spotlight service public accessible. If
>>> so I could try to replicate this. If you do not want send the URL on a
>>> public mailing list feel free to send it directly to me.
>>>
>>>> The
>>>> only clue I have so far is the following message in the console
>>>> where I run
>>>> Stanbol:
>>>> /
>>>> //A servlet request, to the URI
>>>> http://192.168.1.35:8080/enhancer/chain/dbpedia-spotlight, contains
>>>> form
>>>> parameters in the request body but the request body has been
>>>> consumed by the
>>>> servlet or a servlet filter accessing the request parameters. Only
>>>> resource
>>>> methods using @FormParam will work as expected. Resource methods
>>>> consuming
>>>> the request body by other means will not work as expected./
>>>>
>>> This message is triggered by any Request to Stanbol when the
>>> "httpqueryheaders" module is active. It can not be the cause for your
>>> problem.
>>>
>>> Are there any loggings in the Stanbol log file?
>>> What is the exact Chain configuration you are using?
>>>
>>> On the Stanbol Dev Server [1] (nightly build) it seams to work.
>>>
>>> best
>>> Rupert
>>>
>>> [1]http://dev.iks-project.eu:8081/enhancer/chain/dbpedia-spotlight
>>>
>>>> Does anyone know what can be happening??
>>>>
>>>> Regards
>>>>
>>>> This message should be regarded as confidential. If you have
>>>> received this
>>>> email in error please notify the sender and destroy it immediately.
>>>> Statements of intent shall only become binding when confirmed in
>>>> hard copy
>>>> by an authorised signatory.
>>>>
>>>> Zaizi Ltd is registered in England and Wales with the registration
>>>> number
>>>> 6440931. The Registered Office is 222 Westbourne Studios, 242 Acklam
>>>> Road,
>>>> London W10 5JJ, UK.
>>>
>>> -- 
>>> | Rupert Westenthalerrupert.westenthaler@gmail.com
>>> | Bodenlehenstraße 11                             ++43-699-11108907
>>> | A-5500 Bischofshofen
>>
> 
> 
> This message should be regarded as confidential. If you have received
> this email in error please notify the sender and destroy it immediately.
> Statements of intent shall only become binding when confirmed in hard
> copy by an authorised signatory.
> 
> Zaizi Ltd is registered in England and Wales with the registration
> number 6440931. The Registered Office is 222 Westbourne Studios, 242
> Acklam Road, London W10 5JJ, UK.
> 


Re: DBPedia Spotlight Enhancer is not working

Posted by Rafa Haro <rh...@zaizi.com>.
Hi again,

In the post about DBpedia Spotlight and Apache Stanbol Integration by 
Iavor Jelev [1] you can read exactly the following:

*/$chainURL/dbpspotlight/*/
//This chain replicates the functionality of dbpspotlightannotate, by 
chaining dbpspotlightspot and dbpspotlightdisambiguate. Please note that 
langidis run first, and only english texts are processed. In the near 
future, DBpedia Spotlight will support multiple languages and this 
constraint will be adapted accordingly./

Is this maybe a hard-coded restriction?

Regards

[1] 
http://blog.iks-project.eu/dbpedia-spotlight-integration-in-apache-stanbol-2/

El 03/12/12 09:39, Rafa Haro escribió:
> Hi Rupert,
>
> As always, thanks for your help. Inspecting the logs, part of the 
> mystery has clarified. Basically, the problem is the language. I'm 
> trying to test DBPedia Spotlight enhancer with Spanish texts. So, I 
> did a request to the Stanbol Dev Server with a Spanish text and got 
> the same result. Then I configured again my local Stanbol to work with 
> a local installation of DBPedia Spotlight, try again with a Spanish 
> text and this time I can read the following messages in the log file:
> /
> //[Thread-114] 
> org.apache.stanbol.enhancer.engines.langdetect.LanguageDetectionEnhancementEngine 
> language identified: [es:0.999996063192582]//
> //03.12.2012 08:52:55.386 *INFO* [Thread-116] 
> org.apache.stanbol.enhancer.engines.dbpspotlight.utils.SpotlightEngineUtils 
> DBpedia Spotlight can not process ContentItem 
> <urn:content-item-sha1-4e1e021a361ceee0897f81f6e8d4b909072cd04e> 
> because language es is not supported (supported: [en])/
>
> So far, I haven't been able to find anything to change supported 
> languages for the enhancer. I suppose that it should be possible to do 
> that, am I wrong??
>
> Thanks. Regards
>
> El 01/12/12 15:19, Rupert Westenthaler escribió:
>> On Fri, Nov 30, 2012 at 2:14 PM, Rafa Haro<rh...@zaizi.com>  wrote:
>>> Hi all,
>>>
>>> I was trying to test the DBPedia Spotlight enhancer with a local
>>> installation of DBPedia Spotlight in an out-of-the-box Stanbol from the
>>> repository. So, I changed the URL of the service in dbpspotlightannotate
>>> engine to my point to my local service endpoint. When I tested it, the
>>> enhancement chain always stopped at language detection engine. I thought
>>> that maybe there was any error with my local installation, but then I tried
>>> again with the default URL endpoint
>>> (http://spotlight.dbpedia.org/rest/annotate) and got the same result.
>> I have never tried to change the configuration of the service URL so
>> this might be a Bug. Is your Spotlight service public accessible. If
>> so I could try to replicate this. If you do not want send the URL on a
>> public mailing list feel free to send it directly to me.
>>
>>> The
>>> only clue I have so far is the following message in the console where I run
>>> Stanbol:
>>> /
>>> //A servlet request, to the URI
>>> http://192.168.1.35:8080/enhancer/chain/dbpedia-spotlight, contains form
>>> parameters in the request body but the request body has been consumed by the
>>> servlet or a servlet filter accessing the request parameters. Only resource
>>> methods using @FormParam will work as expected. Resource methods consuming
>>> the request body by other means will not work as expected./
>>>
>> This message is triggered by any Request to Stanbol when the
>> "httpqueryheaders" module is active. It can not be the cause for your
>> problem.
>>
>> Are there any loggings in the Stanbol log file?
>> What is the exact Chain configuration you are using?
>>
>> On the Stanbol Dev Server [1] (nightly build) it seams to work.
>>
>> best
>> Rupert
>>
>> [1]http://dev.iks-project.eu:8081/enhancer/chain/dbpedia-spotlight
>>
>>> Does anyone know what can be happening??
>>>
>>> Regards
>>>
>>> This message should be regarded as confidential. If you have received this
>>> email in error please notify the sender and destroy it immediately.
>>> Statements of intent shall only become binding when confirmed in hard copy
>>> by an authorised signatory.
>>>
>>> Zaizi Ltd is registered in England and Wales with the registration number
>>> 6440931. The Registered Office is 222 Westbourne Studios, 242 Acklam Road,
>>> London W10 5JJ, UK.
>>
>> --
>> | Rupert Westenthalerrupert.westenthaler@gmail.com
>> | Bodenlehenstraße 11                             ++43-699-11108907
>> | A-5500 Bischofshofen
>


This message should be regarded as confidential. If you have received this email in error please notify the sender and destroy it immediately. Statements of intent shall only become binding when confirmed in hard copy by an authorised signatory.

Zaizi Ltd is registered in England and Wales with the registration number 6440931. The Registered Office is 222 Westbourne Studios, 242 Acklam Road, London W10 5JJ, UK.

Re: DBPedia Spotlight Enhancer is not working

Posted by Rafa Haro <rh...@zaizi.com>.
Hi Rupert,

As always, thanks for your help. Inspecting the logs, part of the 
mystery has clarified. Basically, the problem is the language. I'm 
trying to test DBPedia Spotlight enhancer with Spanish texts. So, I did 
a request to the Stanbol Dev Server with a Spanish text and got the same 
result. Then I configured again my local Stanbol to work with a local 
installation of DBPedia Spotlight, try again with a Spanish text and 
this time I can read the following messages in the log file:
/
//[Thread-114] 
org.apache.stanbol.enhancer.engines.langdetect.LanguageDetectionEnhancementEngine 
language identified: [es:0.999996063192582]//
//03.12.2012 08:52:55.386 *INFO* [Thread-116] 
org.apache.stanbol.enhancer.engines.dbpspotlight.utils.SpotlightEngineUtils 
DBpedia Spotlight can not process ContentItem 
<urn:content-item-sha1-4e1e021a361ceee0897f81f6e8d4b909072cd04e> because 
language es is not supported (supported: [en])/

So far, I haven't been able to find anything to change supported 
languages for the enhancer. I suppose that it should be possible to do 
that, am I wrong??

Thanks. Regards

El 01/12/12 15:19, Rupert Westenthaler escribió:
> On Fri, Nov 30, 2012 at 2:14 PM, Rafa Haro <rh...@zaizi.com> wrote:
>> Hi all,
>>
>> I was trying to test the DBPedia Spotlight enhancer with a local
>> installation of DBPedia Spotlight in an out-of-the-box Stanbol from the
>> repository. So, I changed the URL of the service in dbpspotlightannotate
>> engine to my point to my local service endpoint. When I tested it, the
>> enhancement chain always stopped at language detection engine. I thought
>> that maybe there was any error with my local installation, but then I tried
>> again with the default URL endpoint
>> (http://spotlight.dbpedia.org/rest/annotate) and got the same result.
> I have never tried to change the configuration of the service URL so
> this might be a Bug. Is your Spotlight service public accessible. If
> so I could try to replicate this. If you do not want send the URL on a
> public mailing list feel free to send it directly to me.
>
>> The
>> only clue I have so far is the following message in the console where I run
>> Stanbol:
>> /
>> //A servlet request, to the URI
>> http://192.168.1.35:8080/enhancer/chain/dbpedia-spotlight, contains form
>> parameters in the request body but the request body has been consumed by the
>> servlet or a servlet filter accessing the request parameters. Only resource
>> methods using @FormParam will work as expected. Resource methods consuming
>> the request body by other means will not work as expected./
>>
> This message is triggered by any Request to Stanbol when the
> "httpqueryheaders" module is active. It can not be the cause for your
> problem.
>
> Are there any loggings in the Stanbol log file?
> What is the exact Chain configuration you are using?
>
> On the Stanbol Dev Server [1] (nightly build) it seams to work.
>
> best
> Rupert
>
> [1] http://dev.iks-project.eu:8081/enhancer/chain/dbpedia-spotlight
>
>> Does anyone know what can be happening??
>>
>> Regards
>>
>> This message should be regarded as confidential. If you have received this
>> email in error please notify the sender and destroy it immediately.
>> Statements of intent shall only become binding when confirmed in hard copy
>> by an authorised signatory.
>>
>> Zaizi Ltd is registered in England and Wales with the registration number
>> 6440931. The Registered Office is 222 Westbourne Studios, 242 Acklam Road,
>> London W10 5JJ, UK.
>
>
> --
> | Rupert Westenthaler             rupert.westenthaler@gmail.com
> | Bodenlehenstraße 11                             ++43-699-11108907
> | A-5500 Bischofshofen


This message should be regarded as confidential. If you have received this email in error please notify the sender and destroy it immediately. Statements of intent shall only become binding when confirmed in hard copy by an authorised signatory.

Zaizi Ltd is registered in England and Wales with the registration number 6440931. The Registered Office is 222 Westbourne Studios, 242 Acklam Road, London W10 5JJ, UK.