You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Original author: @cstockloew (2016-06-10 00:34:54)
It is assumed that the object was created correctly. Therefore, in your example, you should use:
Device d = new Device(..);
which will have the correct type.
BTW: ManagedIndividual is abstract, so you anyway need to create an instance of a subclass.
If this is changed, the matchmaking needs to be revisited to make sure the change does not break anything. I would leave it as it is (maybe add a different method, if needed).
Originally Opened: @amedranogil (2016-06-09 20:24:39)
ManagedIndividual.checkMembership relies on the OntClassInfo information but fails to check the PROP_RDF_TYPE property of the object itself.
Thus if:
ManagedIndividual mi = new ManagedIndividual;
mi.addType(Device.MY_URI,false);
then:
ManagedIndividual.checkMembership(Device.MY_URI,mi) == false
--
From: this issue has been automatically imported from our old issue tracker
The text was updated successfully, but these errors were encountered: