Hi Rupert, Alessandro.
I followed Sebastian's advice and made a complete new and fresh checkout
of the stanbol trunk.
I briefly checked on my ontonet tests tonight and at first sight it
looks like the delete and put requests are now working for me.
For my update test on the entityhub/entity, I now get
curl -i -X PUT -H "Content-Type:application/rdf+xml" -T someEntity
"http://lnv-89012.dfki.uni-sb.de:9001/entityhub/entity?id=http://developer.yahoo.com/javascript/howto-proxy-falseaddress.html&create=false";
HTTP/1.1 100 Continue
HTTP/1.1 400 Bad Request
Accept: application/json
Content-Type: text/plain
Transfer-Encoding: chunked
Server: Jetty(6.1.x)
(So that's exactly what we were talking about).
Let me test and check on everything tomorrow, then I can give you
detailed feedback. I'm sorry for troubling you lately by reporting that
these things didn't work for me. For a possible reason, I can only guess
that my stanbol version got messed up during the last 3
updates/rebuilds, and that it was a bit buggy in the end.
best
melanie
Am 09.07.2012 17:17, schrieb Rupert Westenthaler:
On Mon, Jul 9, 2012 at 4:54 PM, Melanie Reiplinger
<[email protected]> wrote:
"http://<stanbol>/entityhub/entity?id=http://developer.yahoo.com/javascript/howto-proxy-falseaddress.html&create=false";
update the Entity "howto-proxy-falseaddress.html"?
update the Entity "howto-proxy.html"?
something else?
hm, I expected something like: since the "howto-proxy-falseaddress.html"
does not exist, I should get some error because I'm referencig my
to-be-updated entity by a wrong ID. The content of the rdf file should be of
secondary relevance here (because if my ID is not addressing any existing
entity, the update should fail anyway). In fact, I expected that nothing
would be updated in this case. (wouldn't it be strange to update entity
"howto-proxy.html" when I pass some non-existing ID ?)
As the check if the parsed id is present in the parsed data comes
first you should get a "Bad Request" with a an according message.
If the file would contain a triple with the subject
"http://developer.yahoo.com/javascript/howto-proxy-falseaddress.html";
you would get a "Bad Request" with the message telling you that you
can not update an entity that does not exist on the Entityhub.
I will try to use your exact scenario and check if I can reproduce.
If not I will try to temporarily setup an test server for you to
validate on the dev.iks-project.eu server for testing.
best
Rupert
