From: Daniele P. <dp...@gm...> - 2008-02-18 20:28:53
|
On Feb 12, 2008 3:50 PM, Paolo Pessina <pes...@gm...> wrote: > At the moment we implement JDEEP to write the local (and consequently the > global) Xml file at the end of the Eclipse session. If the Vector of > ClassItem is small, there is no problem with this solution, but, if the file > grows to much, it's possible that Eclipse stops the operation leaving the > file in a inconsistent state. In the last release I've optimized the writing class, reducing the interaction of many loop in the XmlWriter and Aggregate classes. The size of the vector for now doesn't seem to be a great problem. > For this reason I think that we would implements a mechanism that at > regular time interval (for example every 30 minutes), writes the two files > managed by JDEEP. Good idea, I'm working on it. I'm implementing a timer that every tot minutes (preferably less than 30) invokes a class that extend java.util.TimerTask which performs a dump of the vector in the xml files. -- "Life would be easier if I had the source code" http://paso.wordpress.com/ |