[owl-s] Thread safety of loading ontologies and performingqueries?

[Jim Andreou]

2009/6/16 Thorsten Möller <Thorsten.Moeller at unibas.ch>

> On Tuesday, June 16, 2009 1:26 PM [GMT+1=CET],
> Jim Andreou <jim.andreou at gmail.com> wrote (with possible deletions):
>
> > Can we make LockNotSupportedException unchecked? It makes my code
> > ugly :( (And there is nothing really the client could do, he must go
> > back to his code and fix whatever thread-safety issue there is!)
> Since I never used locking so far, I never thought about if this
> exception acutally makes sense. Now, after thinking about it, I suggest
> an even simplier solution: LockNotSupportedException will be entirely
> removed and an UnsupportedOperationException is thrown (which is
> unchecked) if the implementation does not support locking. Since the
> current implementation (based on Jena) supports locking no exception
> occurs :-)
>
> If you agree, then this will be yet another change in the large
> refactoring I'm currently working on.
>
> Cheers,
> Thorsten


Sure, this sounds even better - one less class in javadocs too :)
(You could even go a step beyond and remove the "isLockSupported" method too
- I would be curious to see code that actually uses that, and particularly,
what happens in the 'else' part of the check. Nothing useful most probably.)

Thanks Thorsten!

Dimitris
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.mindswap.org/pipermail/owl-s/attachments/20090616/dee4a9ff/attachment.html