-
currently the Variant interface includes an addParameter(Topic) method, but XTM 1.0 also permits elements as children of , so there should probably be an addParameter(Locator) method in the API as well.
Calls to this method would add a Locator instead of a Topic. When one doesn't want to reify the subject of the parameter (such as XTM 'Display') as a Topic...
2006-11-15 03:10:05 UTC in TM4J
-
Not such a simple fix after all. It seems that rather than closing off an open upon receiving the event for a variant, it's creating a new and putting the in that. Because the latter doesn't have a of its own, the element is invalid. This might be happening in the tree walker.
2006-11-15 02:51:27 UTC in TM4J
-
The memory.TopicImpl#removeMergedTopics() method uses an Iterator, which causes a ConcurrentModificationException when the Collection it is operating upon is modified. Changing to a for loop over an array solves this.
2006-11-15 02:30:05 UTC in TM4J
-
The content model in XTM 1.0 for is
(scope?,baseNameString,variant*), but the current
XTMWriter code is putting the baseNameString after the
variants, not before them.
This is a simple fix in XTMWriter of moving the
writeBaseNameString() method call from endBaseName() to
the end of the startBaseName() method.
2006-11-14 04:19:49 UTC in TM4J
