> > Why cache to XML if you're looking for super performance? Wouldn't > > serialized objects be even quicker? I haven't a clue how xjavadoc works > > internally, but my hunch is that it builds an object graph representing > > classes/methods/fields and their @tag data. > > > > Just an idea.... dunno if loading serialized objects is faster than SAX on > > XML files and rebuilding the object graphi, but seems like it would be. > > > > Erik > > Hmmm. Serialized objects were used by NetBeans in the early days to persist > the state of the IDE (user settings, window positioning etc.) and this was > not exactly successful since new versions of classes are persisted > differently and incompatibly...
but thats configuration information yes? In this case, there would be no problem if the cache was corrupt... we can catch the exception (error? geez... hmmm) and dump the corrupt part of the cache and build again... cheers dim _______________________________________________ Xdoclet-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
