YellowGrass

Query a non-existing property for a URI gives an exception

We have a name, annotated with a URI and query a property which does not exist for that name (but for other names), eg. <get-type> name. This gives an InterpreterException, instead of just failing.

get-type calls get-property(|Type()), try(nabl-get-name) and get-index-property(|Type()), which calls nabl-uris and then nabl-get-value, which raises the exception.

Submitted by Guido Wachsmuth on 26 February 2014 at 14:04

Issue Log

On 26 February 2014 at 14:04 Guido Wachsmuth tagged @gohla
On 26 February 2014 at 16:21 Gabriël Konat commented:

Always provide a stack trace (which can be found in the error log) please.

On 26 February 2014 at 16:44 Guido Wachsmuth commented:

This needs to be provided by Daco, who got the exception.

On 26 February 2014 at 18:02 Daco Harkes commented:

I cannot reproduce this bug anymore.

This issue can be closed.

On 5 March 2014 at 14:50 Guido Wachsmuth commented:

This was probably also caused by a non-initialised index/task engine.

On 5 March 2014 at 14:50 Guido Wachsmuth closed this issue.

Log in to post comments