From: SourceForge.net <no...@so...> - 2006-02-18 17:07:45
|
Bugs item #1434160, was opened at 2006-02-18 15:55 Message generated for change (Comment added) made by lheuer You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=391879&aid=1434160&group_id=27895 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: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Lars Heuer (lheuer) Assigned to: Nobody/Anonymous (nobody) Summary: TMAPI Implementation is unstable Initial Comment: The TMAPI implementation of TM4J is unstable. In summary there are the following problems: - Sometimes the wrapping of native TM4J objects to the TMAPI interfaces is forgotten (i.e. see (now closed) bug #1433778) - The update of collections may be slow (i.e. the removeSubjectIdentifier method does not not check if the the collection is really modified but sets the whole subject identifiers to a new value). - Removal of objects is sometimes inefficient. - Contains unused code - The Wrapper cannot handle the wrapping of wrap(Object obj) where obj is an instance of a VariantName. - Sometimes arrays are created without the need to create them. Sometimes the utility methods of java.util.Collections can be used instead of handling everything manually. The attached patch solves the mentioned problems. The patch is against the CVS and makes the TMAPI implementation more stable and efficient, using less memory. ---------------------------------------------------------------------- >Comment By: Lars Heuer (lheuer) Date: 2006-02-18 18:07 Message: Logged In: YES user_id=399396 Added a slightly modified patch that removes an unnecessary call to "checkUpdatesAllowed" in the TopicMapSystemImpl. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=391879&aid=1434160&group_id=27895 |