-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[e-link][explore][ldf] broken on freme 0.4 and later? #10
Comments
I un-ignored the JUnit tests, they work (with the mockup endpoint). |
**I can reproduce the problem. Explore sparql endpoint works:
I checked the logfiles. There is a NullPointerException and a stack trace:
@m1ci any idea whats wrong? |
hard to say, no changes has been done in the recent period |
I tried to find the issue but without success. |
The problem happens on FREME live which still runs the old architecture. Sorry milan this is an old bug :) Does the bug occur on dbpedia only or is the endpoint LDF explore generally broken? |
not really, see bellow :)
Very valid question, just checked and this particular LDF endpoint is broken. The LDF explore API is OK. For example, the ORCID endpoint (http://rv2622.1blu.de:5000/orcid) is working. Here is example:
|
When it happens only at DBPedia then I guess the problem lies within DBPedia LDF endpoint and not within our codes. So we can do nothing about it. I leave the issue open so we can test it again in a few weeks. Maybe it solves itself by the next update in DBPedia. |
Maybe this will be fixed by updating Jena: freme-project/e-Link#69 |
I can not reproduce this anymore, is it fixed? Can we close this? |
The error still occurs. Now the CURL (see first comment) produces
I still think that the problem originates from within DBPedia. |
It is really strange that I get a result if
Btw using endpointType=ldf gives this:
especially: Only triples or default graph data expected : named graph data ignored |
@ArneBinder please do not invest more time on this. We think that this problem is dbpedia specific and the feature is not used by anyone anyways. |
post /e-link/explore ldf
seems to be broken. The following curl does not work:result:
explore sparql still works:
The text was updated successfully, but these errors were encountered: