SynchronizationException is described as "thrown when
the state entity cannot be synchronised with the
underlying persistence mechanism (if any)" - this seems
to imply that if no underlying persistence mechanism is
there (like in the current WSMO4J implementation) this
exception should not be raised. On the contrary, WSMO4J
throws this exception in various unrelated conditions
like for example in WsmoFactoryImpl.getConcept(id) if
the entity with this id is not an instance of Concept.
This SynchronizationException is the only mention of an
underlying persistence mechanism in WSMO-API, I believe
the API doesn't need this mention. If
SynchronizationException is renamed to something more
general, then I believe the existing runtime exceptions
(IllegalArgumentException, ClassCastException etc.) can
be thrown instead in all of WSMO4J. Then the new
renamed SynchronizationException would again be
unnecessary.
I'm against having something like
WsmoApiRuntimeException which is what you seem to turn
this SynchronizationException into.
Log in to post a comment.
