Search Mailing List Archives


Limit search to: Subject & Body Subject Author
Sort by: Reverse Sort
Limit to: All This Week Last Week This Month Last Month
Select Date Range     through    

[protege-discussion] problems with projects in server mode

Henk-Jan Lebbink henkjan at cs.uu.nl
Sun Jan 7 22:46:08 PST 2007


Hi Tania,

On Thu Dec 14 14:21:20 PST 2006 Tania Tudorache wrote:
(quoting from:
https://mailman.stanford.edu/pipermail/protege-discussion/2006-December/000414.html)

> There is also another error (the concurrent modification error) that we
are going to look at.

I have pinpointed the concurrent modification error in the 365 build. It
can be reproduced with the following steps.

1] Create three classes in thing with name: class1, class2 and class3. 2]
Create one slot with name: slot1, value type: instance, allowed classes:
class3, domain: class1.
3] Create one instance in class3.
4] Create one instance in class1; add in slot1 the instance from class3.
5] Add to the types of the instance in class1 the class2.
6] Somehow, you are not paying attention; add to the types of the instance
in class1 the class1.

WARNING: java.util.ConcurrentModificationException --
AbstractSlotWidget.setWidgetValues()

The warning is not that bad; however, the content of slot1 is not
displayed. We can circumvent the bug by manually checking whether classes
occur more than twice (and delete superfluous classes).

Wouldn't it be reasonable that types should only allow one instance of a
class?

With regards,
Henk-Jan.






More information about the protege-discussion mailing list