From: Kal A. <ka...@te...> - 2001-06-15 20:33:31
|
Hi Rich, I've had a look into this and not quite figured out whats going wrong. If both topic maps have an xml:base attribute specified, the XTMBuilder seems to do the right thing and put the fragment identifiers on the xml:base attribute value. If the topic maps do not have an xml:base attribute, then the fragment identifiers get added to a default base URL (http://topicmap.techquila.com/default). Perhaps I am missing something obvious here - do you have a sample of the topic maps which cause this problem that I can have a look at ? Cheers, Kal > -----Original Message----- > From: tm4...@li... > [mailto:tm4...@li...]On Behalf Of Richard > Watson > Sent: 14 June 2001 21:58 > To: TM4J Users > Subject: [TM4J-users] sequence of loading two files > > > Hi all, > > I'm getting a bit better at this stuff and things are working nicely. :) > > I've found something that looks a bit suspicious: > > File "A.xml" and file "B.xml" > File A.xml has an association between #n and #m, both in A.xml. > Both files have correct bases set. > I load both into the same TopicMap using the XTMBuilder. > > Now...two cases: > If I load A.xml into the builder and then B.xml, the association will load > fine. > > If I load B first, then the topicRefs in the association must be "A.xml#n" > and "A.xml#m", or they end up with resourcerefs "B.xml#n" and "B.xml#m". > > This a bug? > > Non-codey question of the day: where are you guys geographically? > > Cheers, > Rich > > > _______________________________________________ > Tm4j-users mailing list > Tm4...@li... > http://lists.sourceforge.net/lists/listinfo/tm4j-users > > |