New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

XTM 1.0 import fails with "cannot reify more than one reifiable object" #77

Closed
GoogleCodeExporter opened this Issue Mar 16, 2015 · 8 comments

Comments

Projects
None yet
1 participant
@GoogleCodeExporter

GoogleCodeExporter commented Mar 16, 2015

Importing an XTM 1.0 file with two associations (duplicate) which each 
have their own reifying topic fails with: "cannot reify more than one 
reifiable object".

Original issue reported on code.google.com by lar...@gmail.com on 16 Jul 2009 at 8:25

@GoogleCodeExporter

This comment has been minimized.

GoogleCodeExporter commented Mar 16, 2015

Original comment by lar...@gmail.com on 16 Jul 2009 at 10:39

  • Changed state: Started
@GoogleCodeExporter

This comment has been minimized.

GoogleCodeExporter commented Mar 16, 2015

Fixed by r325. Test case added.

Original comment by lar...@gmail.com on 16 Jul 2009 at 1:10

  • Changed state: Verified
@GoogleCodeExporter

This comment has been minimized.

GoogleCodeExporter commented Mar 16, 2015

Customer reports that the fix did not work, and retesting with the RDBMS 
backend 
shows that the problem does indeed continue to exist there. Retesting with the 
in-
memory backend does not reproduce the problem.

Original comment by lar...@gmail.com on 20 Jul 2009 at 9:27

  • Changed state: Started
  • Added labels: Component-RDBMS
@GoogleCodeExporter

This comment has been minimized.

GoogleCodeExporter commented Mar 16, 2015

Full traceback:

net.ontopia.topicmaps.xml.InvalidTopicMapException: The topic [rdbms.Topic, 
T623 
{URI|http://testabc.com/xtm/#abn3_977326E1-4E04-4DA4-8A12-ED096BE34716}] cannot 
reify more than one reifiable object. 1: [rdbms.Association, A620, type: 
[rdbms.Topic, T504 {URI|http://testxtm.com/psi/#doc-category-assignment}]] 2: 
[rdbms.Association, A629, type: [rdbms.Topic, T504 
{URI|http://testxtm.com/psi/#doc-
category-assignment}]]
    at net.ontopia.topicmaps.impl.utils.ReificationUtils.reify
(ReificationUtils.java:30)
    at net.ontopia.topicmaps.xml.XTMContentHandler.reify
(XTMContentHandler.java:1022)
    at net.ontopia.topicmaps.xml.XTMContentHandler.addSubjectIdentifier
(XTMContentHandler.java:1346)
    at net.ontopia.topicmaps.xml.XTMContentHandler.registerSubjectIndicator
(XTMContentHandler.java:1141)
    at net.ontopia.topicmaps.xml.XTMContentHandler.createTopicFromLazyTopic
(XTMContentHandler.java:1494)
    at net.ontopia.topicmaps.xml.XTMContentHandler.getParentTopic
(XTMContentHandler.java:1454)
    at net.ontopia.topicmaps.xml.XTMContentHandler.startElement
(XTMContentHandler.java:468)
    at net.ontopia.topicmaps.xml.XTMValidatingContentHandler.startElement
(XTMValidatingContentHandler.java:80)
    at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1488)
    at org.apache.crimson.parser.Parser2.content(Parser2.java:1779)
    at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1507)
    at org.apache.crimson.parser.Parser2.content(Parser2.java:1779)
    at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1507)
    at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:500)
    at org.apache.crimson.parser.Parser2.parse(Parser2.java:305)
    at org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:442)
    at net.ontopia.topicmaps.xml.XTMTopicMapReader.read
(XTMTopicMapReader.java:226)
    at net.ontopia.topicmaps.xml.XTMTopicMapReader.readAll
(XTMTopicMapReader.java:272)
    at net.ontopia.topicmaps.xml.XTMTopicMapReader.importInto
(XTMTopicMapReader.java:291)
    at net.ontopia.topicmaps.cmdlineutils.rdbms.RDBMSImport.main
(RDBMSImport.java:93)

Original comment by lar...@gmail.com on 20 Jul 2009 at 9:30

@GoogleCodeExporter

This comment has been minimized.

GoogleCodeExporter commented Mar 16, 2015

Fixed by r342. Test case added.

Original comment by lar...@gmail.com on 20 Jul 2009 at 10:09

  • Changed state: Fixed
@GoogleCodeExporter

This comment has been minimized.

GoogleCodeExporter commented Mar 16, 2015

We have tested XTM file import into database using 
XTMTopicMapReader.importInto() 
API and it succeeds the exection and data getting populated in DB.

But when we test Synchronize update of XTM file into database which contains 
two 
associations(duplicate) and corresponding two reified topics using 
TopicMapSynchronizer.update() API, all reified_id columns in many tables still 
contains NULL values.

Original comment by joeprad...@gmail.com on 20 Jul 2009 at 4:55

@GoogleCodeExporter

This comment has been minimized.

GoogleCodeExporter commented Mar 16, 2015

Hi Joe,

> We have tested XTM file import into database using 
XTMTopicMapReader.importInto() 
> API and it succeeds the exection and data getting populated in DB.

Excellent. That means that this issue (#77) is solved.

> But when we test Synchronize update ...

Ok. That means we still have an issue in TMSync. That is a separate issue, 
though. 
Please report it separately.

Original comment by lar...@gmail.com on 20 Jul 2009 at 5:05

@GoogleCodeExporter

This comment has been minimized.

GoogleCodeExporter commented Mar 16, 2015

Original comment by lar...@gmail.com on 1 Sep 2009 at 11:43

  • Added labels: Release5.0.1
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment