From: Conal T. <Con...@vu...> - 2004-09-27 06:38:51
|
I recently switched from Hibernate to the In-Memory back-end and I now = have a slight problem with persistence of subject indicators. With the = In-Memory back-end you have to write the topic map to an XTM file to = persist it. I THINK that all my subject indicators are in the topic map = in memory, but are not written to my XTM, and this causes a problem next = time I load the map.=20 My TM is built by merging a bunch of XTM files which are harvested from = various sources, and also including some ontological topicmaps. For = instance I have an ontology file with a base-locator of = http://www.nzetc.org/tm/harvest/xtm/nzetc-ontology.xtm which includes = for instance a topic with id =3D "pdf-file". When I save my central = (merged) XTM file I get the topic written out just the same way, as a = topic with id=3D"pdf-file", but with no<subjectIdentity>. Because the = base locator of the merged file is different to the base locator of the = ontology, I won't be able to refer to the same topic in a different = file, using a full URI: http://www.nzetc.org/tm/harvest/xtm/nzetc-ontology.xtm#pdf-file ... because this subject indicator just isn't present in the (merged) = XTM file I save. I've looked at the source code of the TopicMapWalker and the XTMWriter = and it looks like it should work, but I get nothing in my output. So long as I have Cocoon running, and my topic map in memory, then I can = merge topic maps into it and everything is fine; the topics merge as = they should (this is why I think the subject indicators ARE present in = memory), but as soon as I save the merged XTM and reload it, then my = original subject indicators are gone and everything turns to custard. Any ideas? Con |