Menu
▾
▴
tinytim-discuss — Discussions relating to tinyTiM
You can subscribe to this list here.
| 2008 |
Jan
|
Feb
|
Mar
|
Apr
(30) |
May
(4) |
Jun
(19) |
Jul
(36) |
Aug
(21) |
Sep
(10) |
Oct
(18) |
Nov
(43) |
Dec
(7) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2009 |
Jan
(5) |
Feb
(18) |
Mar
(6) |
Apr
|
May
|
Jun
(6) |
Jul
(21) |
Aug
(47) |
Sep
(3) |
Oct
|
Nov
(5) |
Dec
|
| 2010 |
Jan
(8) |
Feb
|
Mar
(5) |
Apr
(2) |
May
|
Jun
(14) |
Jul
(2) |
Aug
|
Sep
(4) |
Oct
(4) |
Nov
|
Dec
|
| 2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
(4) |
Nov
|
Dec
|
|
From: Stefan L. <li...@ap...> - 2008-07-02 12:13:32
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 a sounds good, but do we need an IOFactory? or let the user simple call new XTM20Serializer(...) ? Lars Heuer wrote: > [...] >> IMO it would be nice if we'd create a generic API to import topic >> maps, independently of the concrete syntax, so I'd favour .io. > > Maybe the proposal was a bit vague, here possible layouts I'd prefer: > > a) > org.tinytim.io: > * Deserializer (interface) > * Serializer (interface) > > org.tinytim.io.xtm > * XTMDeserializer > * XTMSerializer (or XTM10Serializer and XTM20Serializer) > > org.tinytim.io.another-syntax > * AnotherSyntaxDeserializer > * ... > > b) > org.tinytim.io: > * Deserializer (interface) > * Serializer (interface) > * XTMDeserializer > * XTMSerializer (or XTM10/XTM20Serializer) > * AnotherSyntaxDeserializer > > > Personally, I like (a) more. > > > Best regards, > Lars -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIa2+wbsixtqnWg1oRAoDQAKCP/FNkJHWpNZL6eeso6bU5DYTGqgCfb3Sl wOclTeSroHA5rmk2QFBAbOw= =+dQ5 -----END PGP SIGNATURE----- |
|
From: Lars H. <he...@se...> - 2008-07-02 12:08:38
|
[...] > IMO it would be nice if we'd create a generic API to import topic > maps, independently of the concrete syntax, so I'd favour .io. Maybe the proposal was a bit vague, here possible layouts I'd prefer: a) org.tinytim.io: * Deserializer (interface) * Serializer (interface) org.tinytim.io.xtm * XTMDeserializer * XTMSerializer (or XTM10Serializer and XTM20Serializer) org.tinytim.io.another-syntax * AnotherSyntaxDeserializer * ... b) org.tinytim.io: * Deserializer (interface) * Serializer (interface) * XTMDeserializer * XTMSerializer (or XTM10/XTM20Serializer) * AnotherSyntaxDeserializer Personally, I like (a) more. Best regards, Lars -- Semagia <http://www.semagia.com> |
|
From: Lars H. <he...@se...> - 2008-07-02 11:59:38
|
Hi Stefan, [...] > convinced, but we need to find a name, tinytim-io or tinytim-xtm > i would prefer tinytim-xtm > what you think? IMO it would be nice if we'd create a generic API to import topic maps, independently of the concrete syntax, so I'd favour .io. Within the .io package we can provide a XTMDeserializer, LTMDeserializer, WhateverDeserializer which would implement a generic Deserializer interface. The Deserializer interface may be very primitive, just a "parse" method which takes a Stream / Reader / File / URL. Not sure if we want to provide other syntaxes != XTM, but we'd be forward-compatible. ;) If you implement the XTMDeserializer, you may want to use tinyTiM's "native" API and not TMAPI, because the the native API provides faster lookups for Topics than the TMAPI TopicsIndex. Best regards, Lars -- Semagia <http://www.semagia.com> |
|
From: Stefan L. <li...@ap...> - 2008-07-02 07:35:18
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Lars Heuer wrote: > Hi Stefan, > > [StAX deserializer] >> OK, i hope to find some time in the nights ahead, i want to commit it to tinyTIM directly no >> subpackage, please vote! > > IMO a subpackage would be better, otherwise the .core would rely on > StAX for no reason. convinced, but we need to find a name, tinytim-io or tinytim-xtm i would prefer tinytim-xtm what you think? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIay56bsixtqnWg1oRAp8nAJ47Udqawy1HLIC0dJFZED6C5fDPjQCeMqEM u2Xoh99KUuwf3e0PO6111oA= =j2m8 -----END PGP SIGNATURE----- |
|
From: Lars H. <he...@se...> - 2008-07-01 17:08:41
|
[...] > Okay, then I'll rename ".io" into ".mio" and leave the rest up to you. Done. Best regards, Lars -- Semagia <http://www.semagia.com> |
|
From: Lars H. <he...@se...> - 2008-07-01 15:53:45
|
Hi Stefan, [StAX deserializer] > OK, i hope to find some time in the nights ahead, i want to commit it to tinyTIM directly no > subpackage, please vote! IMO a subpackage would be better, otherwise the .core would rely on StAX for no reason. [Package reorg.] >> * Leave the MapInputHandler in the tinytim-io package or put it into a >> new package "tinytim-mio". > +1 for renaming to tinytim-mio (btw. can subprojects be renamed?) Yes, IIRC SVN provides a command for renaming. Maybe it's just "move". Not sure. But it is possible. >> * Replace TopicMapImporter with something that does not use MIO > which TopicMapImporter? This one: <http://tinytim.svn.sourceforge.net/viewvc/tinytim/tinytim-io/trunk/src/main/java/org/tinytim/io/TopicMapImporter.java?view=markup> But maybe it should also moved into the .mio package since it automates the search for a suitable MIO deserializer. Okay, then I'll rename ".io" into ".mio" and leave the rest up to you. Best regards, Lars -- Semagia <http://www.semagia.com> |
|
From: Stefan L. <li...@ap...> - 2008-07-01 14:50:44
|
Hi, >> i would prefer to "fix" the tmapi-utils parser. Not just fixing it, >> but using latest StAX parser and api. This design is easier to >> understand compared to a callback-handler / stackusing parser. > > Okay, no problem. Will you fix it? Should be straight forward, since OK, i hope to find some time in the nights ahead, i want to commit it to tinyTIM directly no subpackage, please vote! > I have a TestCase impl. that does the work more or less automatically, > I'll contribute it this week to the CXTM subproject. take your time, first i will redesign it and then we will test it with your nice stuff. >> i think the adapter (not the mio libraries) could stay as a part of >> the project, for example as tinytim-mio-xtm and tinytim-mio-cxtm, >> but we need to provide a very very simple way of parsing and writing >> xtm 1.0/2.0 wihtin the project, with all sources. > > Hmm... . The CXTM package has nothing to do with MIO. And we need just > one "tinytim-mio" package, since you need only one concrete adapter to > "parse" every syntax you can think of. ;) > > Proposal: > * Leave tinytim-cxtm as it is right +1, no dependencies to mio > * Leave the MapInputHandler in the tinytim-io package or put it into a > new package "tinytim-mio". +1 for renaming to tinytim-mio (btw. can subprojects be renamed?) > * Replace TopicMapImporter with something that does not use MIO which TopicMapImporter? |
|
From: Lars H. <he...@se...> - 2008-07-01 13:17:52
|
Hi Stefan, > i would prefer to "fix" the tmapi-utils parser. Not just fixing it, > but using latest StAX parser and api. This design is easier to > understand compared to a callback-handler / stackusing parser. Okay, no problem. Will you fix it? Should be straight forward, since we have a CXTM serializer. Just import every topic map from <http://cxtm-tests.cvs.sourceforge.net/cxtm-tests/cxtm-tests/xtm1/in/> and <http://cxtm-tests.cvs.sourceforge.net/cxtm-tests/cxtm-tests/xtm2/in/> and check if the output is identical to the output in the "baseline" directory. I have a TestCase impl. that does the work more or less automatically, I'll contribute it this week to the CXTM subproject. > i think the adapter (not the mio libraries) could stay as a part of > the project, for example as tinytim-mio-xtm and tinytim-mio-cxtm, > but we need to provide a very very simple way of parsing and writing > xtm 1.0/2.0 wihtin the project, with all sources. Hmm... . The CXTM package has nothing to do with MIO. And we need just one "tinytim-mio" package, since you need only one concrete adapter to "parse" every syntax you can think of. ;) Proposal: * Leave tinytim-cxtm as it is * Leave the MapInputHandler in the tinytim-io package or put it into a new package "tinytim-mio". * Replace TopicMapImporter with something that does not use MIO Reasonable? Best regards, Lars -- Semagia <http://www.semagia.com> |
|
From: Stefan L. <li...@ap...> - 2008-07-01 10:51:06
|
hi, Lars Heuer wrote: > Hi all, > > Recently, there were some bug reports which are more related to MIO than to > tinyTiM. So, the question is, if we want that MIO becomes the default import > mechanism or not. We can either fix and use tmapi-utils or we develop a > dedicated importer for tinyTiM. i would prefer to "fix" the tmapi-utils parser. Not just fixing it, but using latest StAX parser and api. This design is easier to understand compared to a callback-handler / stackusing parser. the goal of tinyTIM was always to be as simple as possible, thats why so many students that started with topic maps used tinytim and tmapi-utils parser, cause they understood the source code. > What do you think? I am open minded, I'd use tinyTiM's MIO adaptor > for testing purposes anyway, so I don't care if the adaptor is part of > this project or if I keep it as personal project. i think the adapter (not the mio libraries) could stay as a part of the project, for example as tinytim-mio-xtm and tinytim-mio-cxtm, but we need to provide a very very simple way of parsing and writing xtm 1.0/2.0 wihtin the project, with all sources. So maybe we can migrate the tmapi-utils parser to tinytim project thoughts? stefan |
|
From: Lars H. <he...@se...> - 2008-06-29 19:52:20
|
Hi all, Recently, there were some bug reports which are more related to MIO than to tinyTiM. So, the question is, if we want that MIO becomes the default import mechanism or not. We can either fix and use tmapi-utils or we develop a dedicated importer for tinyTiM. The advantage of MIO is, that it is independent of a particular syntax. A small tinyTiM-related adaptor interprets the events from a MIO deserializer and translates them into tinyTiM's Topic Maps constructs. If someone writes a MIO deserializer for syntax XY it is immediately usable by tinyTiM. The disadvantage of MIO is, that it is not controlled by this project, but it is an independent project controlled by me. ;) The license shouldn't be be a problem, because MIO will be released under a Sleepycat-style license, maybe the API will be published in the future under another license to support a more widely adoption, but the first versions will use the Sleepycat lic. and the first deserializers will use that license also. What do you think? I am open minded, I'd use tinyTiM's MIO adaptor for testing purposes anyway, so I don't care if the adaptor is part of this project or if I keep it as personal project. Sleepycat Lic.: <http://opensource.org/licenses/sleepycat.php> Best regards, Lars -- Semagia <http://www.semagia.com/> |
|
From: SourceForge.net <no...@so...> - 2008-06-29 13:24:38
|
Bugs item #2004575, was opened at 2008-06-28 00:48 Message generated for change (Comment added) made by lheuer You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=631664&aid=2004575&group_id=102341 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: I/O Group: None >Status: Closed >Resolution: Invalid Priority: 5 Private: No Submitted By: Stefan Lischke (lischke2) Assigned to: Nobody/Anonymous (nobody) Summary: More details when error in parsing Initial Comment: when there is an error in Parsing (e.g. non xtm conform) there should be more information whats missing or in the wrong place in which line.. dunno if there can be done that much with this old fashioned sax parser. ---------------------------------------------------------------------- >Comment By: Lars Heuer (lheuer) Date: 2008-06-29 15:24 Message: Logged In: YES user_id=399396 Originator: NO It would be possible to include the line # and column #, but this is also a MIO problem, not a tinyTiM problem. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=631664&aid=2004575&group_id=102341 |
|
From: SourceForge.net <no...@so...> - 2008-06-29 12:20:11
|
Bugs item #2004624, was opened at 2008-06-28 01:48 Message generated for change (Comment added) made by lheuer You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=631664&aid=2004624&group_id=102341 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: I/O Group: None >Status: Pending >Resolution: Later Priority: 9 Private: No Submitted By: Stefan Lischke (lischke2) >Assigned to: Lars Heuer (lheuer) Summary: Roles are not imported Initial Comment: Roles of Associations are not imported. the startRole() or startPlayer() methods of the MapInputHandler are never called. See org.tinytim.io.ParseRolesTest.testBugImportRoles2() btw. its not so good to debug, and understand code, if there is code used, from which i can not see the code (semagia-mio) ---------------------------------------------------------------------- >Comment By: Lars Heuer (lheuer) Date: 2008-06-29 14:20 Message: Logged In: YES user_id=399396 Originator: NO This seems to be a MIO problem; the external lib has to be fixed, not tinyTiM. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=631664&aid=2004624&group_id=102341 |
|
From: SourceForge.net <no...@so...> - 2008-06-29 12:17:39
|
Bugs item #2004544, was opened at 2008-06-28 00:00 Message generated for change (Settings changed) made by lheuer You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=631664&aid=2004544&group_id=102341 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Core Group: None >Status: Closed >Resolution: Invalid Priority: 5 Private: No Submitted By: Stefan Lischke (lischke2) Assigned to: Nobody/Anonymous (nobody) Summary: The feature 'http://tmapi.org/features/automerge/' is unknow Initial Comment: i just wanted to test an old tmapi application and latest alpha2 and i get org.tmapi.core.FeatureNotRecognizedException: The feature 'http://tmapi.org/features/automerge/' is unknown at org.tinytim.TopicMapSystemFactoryImpl.reportFeatureNotRecognized(Unknown Source) at org.tinytim.TopicMapSystemFactoryImpl.setFeature(Unknown Source) its by design? i remember it should throw a not supported exception when not implemented yet? ---------------------------------------------------------------------- Comment By: Lars Heuer (lheuer) Date: 2008-06-29 13:30 Message: Logged In: YES user_id=399396 Originator: NO Acc. to the TMAPI docs the feature string is not <http://tmapi.org/features/automerge/> but <http://tmapi.org/features/automerge>. If you try the feature string without a trailing slash, you should get a FeatureUnsupported exception. ---------------------------------------------------------------------- Comment By: Stefan Lischke (lischke2) Date: 2008-06-28 00:05 Message: Logged In: YES user_id=646968 Originator: YES just testing the report to ML function ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=631664&aid=2004544&group_id=102341 |
|
From: SourceForge.net <no...@so...> - 2008-06-29 12:14:19
|
Bugs item #2004618, was opened at 2008-06-28 01:38 Message generated for change (Comment added) made by lheuer You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=631664&aid=2004618&group_id=102341 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: I/O Group: None >Status: Closed >Resolution: Invalid Priority: 5 Private: No Submitted By: Stefan Lischke (lischke2) Assigned to: Nobody/Anonymous (nobody) Summary: Broken TopicMaps are imported without error Initial Comment: if there is an association or topic with a topicref in instanceOf which references a non existing topic, there should be an Exception instead of creating empty stub topics. this behavior might be ok when using resourceRef. see: src/test/java/org.tinytim.io.ParseRolesTest.testBugImportWithoutException() ---------------------------------------------------------------------- >Comment By: Lars Heuer (lheuer) Date: 2008-06-29 14:14 Message: Logged In: YES user_id=399396 Originator: NO Even if that topic is not not mentioned explicitly in the document via <topic id="something/> a topic with the id "something" is created if that id is used within a topicRef. That is no error acc. to the XTM spec. ---------------------------------------------------------------------- Comment By: Stefan Lischke (lischke2) Date: 2008-06-28 02:09 Message: Logged In: YES user_id=646968 Originator: YES i checked this against tmapi-utils xtmparser and he imports the xtm also without any error message, so this error might be invalid. Please comment and set to invalid if d'accord ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=631664&aid=2004618&group_id=102341 |
|
From: SourceForge.net <no...@so...> - 2008-06-29 11:29:51
|
Bugs item #2004544, was opened at 2008-06-28 00:00 Message generated for change (Comment added) made by lheuer You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=631664&aid=2004544&group_id=102341 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Core Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Stefan Lischke (lischke2) Assigned to: Nobody/Anonymous (nobody) Summary: The feature 'http://tmapi.org/features/automerge/' is unknow Initial Comment: i just wanted to test an old tmapi application and latest alpha2 and i get org.tmapi.core.FeatureNotRecognizedException: The feature 'http://tmapi.org/features/automerge/' is unknown at org.tinytim.TopicMapSystemFactoryImpl.reportFeatureNotRecognized(Unknown Source) at org.tinytim.TopicMapSystemFactoryImpl.setFeature(Unknown Source) its by design? i remember it should throw a not supported exception when not implemented yet? ---------------------------------------------------------------------- >Comment By: Lars Heuer (lheuer) Date: 2008-06-29 13:30 Message: Logged In: YES user_id=399396 Originator: NO Acc. to the TMAPI docs the feature string is not <http://tmapi.org/features/automerge/> but <http://tmapi.org/features/automerge>. If you try the feature string without a trailing slash, you should get a FeatureUnsupported exception. ---------------------------------------------------------------------- Comment By: Stefan Lischke (lischke2) Date: 2008-06-28 00:05 Message: Logged In: YES user_id=646968 Originator: YES just testing the report to ML function ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=631664&aid=2004544&group_id=102341 |
|
From: Markus U. <mar...@gm...> - 2008-06-28 15:16:31
|
Hi, 2008/6/28 Lars Heuer <he...@se...>: > Right, or we use Utilities like OneJar (not sure if that works since > we need the API and an implementation of SLF4J). Thanks, I never heard of One-JAR before :) While it seems more sane than repackaging (sic!) all classes from multiple JARs (we used to deploy a _huge_ "3rdparty.jar" at work, shudder), however, I wouldn't do that _per default_. The more "modules"/"engines" you combine, the higher the possibility that you end up with multiple versions of the same archive (e.g., log4j). While this may not always be a problem, sometimes you _need_ to update--and in this situation, it is less obvious that a certain version of the library in question is contained here or there. (Of course, you documented it and remembered to use find/grep/... just to be sure, but there's always Murphy's Law :)) Therefore, I'd suggest that the possibility to use One-JAR is documented in a README file if somebody really wants to deploy a single JAR, but it's not used as part of the build process. (Also, I didn't look whether this approach can be used repeatedly, i.e., if one would combine tinyTiM with other libraries needed by the main application.) Hmmm... maybe we stick with the java.logging for the 1.5 series and wait for > other opinions and may switch to SLF4J in the 2.0 branch (if TMAPI 2.0 > become reality). > Eh... you really want to wait THAT LONG? (Sorry, just kidding >:)) I could live with that, too, of course--though I'd still say it's better to propagate good libraries/facades early as long as they're rather lightweight ;) Ad astra, Markus |
|
From: Lars H. <he...@se...> - 2008-06-28 13:46:52
|
Hi Stefan, [...] > zu dem sl4j, klar facaden sind immer gut, hätte nur ein bedenken für die leute die bisher tinyTIM in > Applets benutzt haben, die müssen nur die logging jars mit reinpacken. Right, or we use Utilities like OneJar (not sure if that works since we need the API and an implementation of SLF4J). Hmmm... maybe we stick with the java.logging for the 1.5 series and wait for other opinions and may switch to SLF4J in the 2.0 branch (if TMAPI 2.0 become reality). BTW, MIO requires SLF4J anyway, but MIO is independent of tinyTiM. Markus, what do you think? Best regards, Lars -- Semagia <http://www.semagia.com/> |
|
From: SourceForge.net <no...@so...> - 2008-06-28 00:09:03
|
Bugs item #2004618, was opened at 2008-06-28 01:38 Message generated for change (Comment added) made by lischke2 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=631664&aid=2004618&group_id=102341 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: I/O Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Stefan Lischke (lischke2) Assigned to: Nobody/Anonymous (nobody) Summary: Broken TopicMaps are imported without error Initial Comment: if there is an association or topic with a topicref in instanceOf which references a non existing topic, there should be an Exception instead of creating empty stub topics. this behavior might be ok when using resourceRef. see: src/test/java/org.tinytim.io.ParseRolesTest.testBugImportWithoutException() ---------------------------------------------------------------------- >Comment By: Stefan Lischke (lischke2) Date: 2008-06-28 02:09 Message: Logged In: YES user_id=646968 Originator: YES i checked this against tmapi-utils xtmparser and he imports the xtm also without any error message, so this error might be invalid. Please comment and set to invalid if d'accord ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=631664&aid=2004618&group_id=102341 |
|
From: SourceForge.net <no...@so...> - 2008-06-27 23:54:47
|
Bugs item #2004628, was opened at 2008-06-28 01:54 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=631664&aid=2004628&group_id=102341 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Documentation Group: None Status: Open Resolution: None Priority: 9 Private: No Submitted By: Stefan Lischke (lischke2) Assigned to: Lars Heuer (lheuer) Summary: Missing old Documentation referenced from tmapi-utils projet Initial Comment: the tmapi-utils start page does reference a tutorial which is missing http://tinytim.sourceforge.net/tinyTIM/docs/ar01s03s03.html please restore the docs folder ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=631664&aid=2004628&group_id=102341 |
|
From: SourceForge.net <no...@so...> - 2008-06-27 23:48:02
|
Bugs item #2004624, was opened at 2008-06-28 01:48 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=631664&aid=2004624&group_id=102341 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: I/O Group: None Status: Open Resolution: None Priority: 9 Private: No Submitted By: Stefan Lischke (lischke2) Assigned to: Nobody/Anonymous (nobody) Summary: Roles are not imported Initial Comment: Roles of Associations are not imported. the startRole() or startPlayer() methods of the MapInputHandler are never called. See org.tinytim.io.ParseRolesTest.testBugImportRoles2() btw. its not so good to debug, and understand code, if there is code used, from which i can not see the code (semagia-mio) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=631664&aid=2004624&group_id=102341 |
|
From: SourceForge.net <no...@so...> - 2008-06-27 23:38:41
|
Bugs item #2004618, was opened at 2008-06-28 01:38 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=631664&aid=2004618&group_id=102341 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: I/O Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Stefan Lischke (lischke2) Assigned to: Nobody/Anonymous (nobody) Summary: Broken TopicMaps are imported without error Initial Comment: if there is an association or topic with a topicref in instanceOf which references a non existing topic, there should be an Exception instead of creating empty stub topics. this behavior might be ok when using resourceRef. see: src/test/java/org.tinytim.io.ParseRolesTest.testBugImportWithoutException() ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=631664&aid=2004618&group_id=102341 |
|
From: SourceForge.net <no...@so...> - 2008-06-27 22:48:13
|
Bugs item #2004575, was opened at 2008-06-28 00:48 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=631664&aid=2004575&group_id=102341 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: I/O Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Stefan Lischke (lischke2) Assigned to: Nobody/Anonymous (nobody) Summary: More details when error in parsing Initial Comment: when there is an error in Parsing (e.g. non xtm conform) there should be more information whats missing or in the wrong place in which line.. dunno if there can be done that much with this old fashioned sax parser. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=631664&aid=2004575&group_id=102341 |
|
From: SourceForge.net <no...@so...> - 2008-06-27 22:31:43
|
Bugs item #2004566, was opened at 2008-06-28 00:31 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=631664&aid=2004566&group_id=102341 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Documentation Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Stefan Lischke (lischke2) Assigned to: Nobody/Anonymous (nobody) Summary: How to import/write an XTM File Initial Comment: without looking at the sourcecode i do not know how to import and write an xtm file. i edited the wikifrontpage and added a site http://tinytim.wiki.sourceforge.net/tinytim-io ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=631664&aid=2004566&group_id=102341 |
|
From: SourceForge.net <no...@so...> - 2008-06-27 22:05:02
|
Bugs item #2004544, was opened at 2008-06-28 00:00 Message generated for change (Comment added) made by lischke2 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=631664&aid=2004544&group_id=102341 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Core Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Stefan Lischke (lischke2) Assigned to: Nobody/Anonymous (nobody) Summary: The feature 'http://tmapi.org/features/automerge/' is unknow Initial Comment: i just wanted to test an old tmapi application and latest alpha2 and i get org.tmapi.core.FeatureNotRecognizedException: The feature 'http://tmapi.org/features/automerge/' is unknown at org.tinytim.TopicMapSystemFactoryImpl.reportFeatureNotRecognized(Unknown Source) at org.tinytim.TopicMapSystemFactoryImpl.setFeature(Unknown Source) its by design? i remember it should throw a not supported exception when not implemented yet? ---------------------------------------------------------------------- >Comment By: Stefan Lischke (lischke2) Date: 2008-06-28 00:05 Message: Logged In: YES user_id=646968 Originator: YES just testing the report to ML function ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=631664&aid=2004544&group_id=102341 |
|
From: Stefan L. <li...@ap...> - 2008-06-27 15:37:44
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Lars, Ich hoffe ich habe mit meiner provokationsmail auf topicmapmail keine zu schlechte laune gemacht, aber ich seh dich seit wochen überall ordentlich posten und ews scheint nichts zurückzukommen. zu dem sl4j, klar facaden sind immer gut, hätte nur ein bedenken für die leute die bisher tinyTIM in Applets benutzt haben, die müssen nur die logging jars mit reinpacken. kriegen wir es nicht clever hin, das logging pluggable zu halten, so dass man es auch ohne logging betreiben kann. Wer es mit haben möchte, der kann ja gerne die beiden jars reinpacken was meinste? Lars Heuer wrote: > Hi Stefan, > > [Using Java Logging] >> I totally agree, we should keep it as simple as possible without any >> additional jars. > >> as a programmer i'm only used to log4j, so i don't know much about >> the java logging api and its pros and cons. > > Markus Ueberall suggested to move to SLF4J <http://www.slf4j.org/>. > Through this facade nearly all logging frameworks are supported > (commons logging, log4j, ...). > > If we'd move to SLF4J the user can use her favourite logging framework > by adding the particular lib to the class path. > > AFAIK, tinyTiM itself does not use any logging (yet). The CXTM > serializer uses logging. > > If we use SLF4J, we need two small jars (the SLF4J API and one of the > implementations, i.e. the one which uses Java logging). > > What do you think? > > Best regards, > Lars -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIZQgUbsixtqnWg1oRAvTLAJ4i38kWENsZ1gD2iREbGo9Xq5mFnQCgkJzf NjvO3CIapwUIB6BhBheLxeQ= =6ngx -----END PGP SIGNATURE----- |
7 messages has been excluded from this view by a project administrator.
