>As far as I know, currently, there is no capability to serialize the DTM
>once it is built and then deserialize it under a new DTMManager.

That's correct, there isn't. It could be done -- actually, I'd suggest that
the right answer would be to make it Exportable rather than Serializable,
since some of the data is redundant (for performance) and should be
reconstructed rather than being saved. That could also deal with binding
the connections to the DTMManager it was being loaded into.

However, the amount of data-patching that would be required to make this
work makes me wonder if it would really be worthwhile. In most cases, the
best "serialized form" for XML is XML. Formatters/parsers have historically
been much slower than serializers/deserializers, though I'll admit they may
consume a lot more codespace.

Xalan's current serializer is not as fast as it should be. We're working on
that. This might actually be a better answer to your question.


If there's a real demand for this function, someone could try to find the
cycles to implement it and report on whether it really buys us anything or
not...

Reply via email to