search

tmlab / majortom

The MaJorToM ( Merging Topic Maps Engine ) project was founded to develop a lightweight, merging and flexible Topic Maps engine satisfying different business use cases. The engine provides a couple of new features above to other engines based on the Topic Maps API version 2.0.
1 stars 1 forks source link

setting the player of a role leads to empty Changeset #58

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. create association with a role with History off and create Topic otherPlayer
2. role.setType(otherPlayer) with Histoy on
3. call revisionIndex.firstRevision.changeSet

What is the expected output? What do you see instead?
A changeSet with one change of type "TYPE_SET".
Instead: empty changeSet and the next revision holds the information I expected 
in the first (empty) one.

Original issue reported on code.google.com by schulze....@googlemail.com on 20 Sep 2010 at 7:28

GoogleCodeExporter commented 9 years ago 
Sorry, confused setType and setPlayer.

Original comment by schulze....@googlemail.com on 20 Sep 2010 at 7:30