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

Occurrences non-existant in Transaction #83

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Take an ITopicMap instance with at least one topic which in turn has at 
least one occurrence.
2. Create a Transaction from that ITopicMap.
3. Try to access an occurrence attached to a topic inside the transaction 
context.

What is the expected output? What do you see instead?
Instead of a set of occurrences one gets an empty set.

What version of the product are you using? On what operating system?
The issue occured using both the latest release (version 1.1.1) and the current 
revision in the hg repository (274).
I'm running Debian Sid (kernel 2.6.38-1-amd64) with openjdk-6 (version 
6b18-1.8.7-2). However, that's very likely not relevant to the issue.

Please provide any additional information below.
Taking a topic from the original topic map, getOccurrences() correctly returns 
a set of occurrences. Executing the same method taking the same topic from the 
transaction, an empty set is returned.

Original issue reported on code.google.com by brog.per...@gmail.com on 24 Mar 2011 at 1:46

GoogleCodeExporter commented 9 years ago 
Which topic map store do you use? JDBC or Memory?

Original comment by Sven.Kro...@googlemail.com on 24 Mar 2011 at 2:23

GoogleCodeExporter commented 9 years ago 
JDBC

Original comment by h.niederhausen@googlemail.com on 24 Mar 2011 at 2:37

GoogleCodeExporter commented 9 years ago

Original comment by Sven.Kro...@googlemail.com on 4 Apr 2011 at 7:50

GoogleCodeExporter commented 9 years ago 
I am sorry, but I cannot reproduce this error. In the example case all works 
fine. Can you please at a code snippet to show the problem.

Original comment by Sven.Kro...@googlemail.com on 4 Apr 2011 at 10:53

GoogleCodeExporter commented 9 years ago

Original comment by Sven.Kro...@googlemail.com on 15 Apr 2011 at 9:08