On Monday, May 6, 2002, at 04:12 PM, Fernando Padilla wrote:
hello.
I would like to open up a topic for discussing among the Xindice community.
I don't think it should be Xindice's responsibility to maintain a proper(correct) XML serializing code. Attempting to do so will lead to improper XML serialization. And I am willing to wager that the use of our own implementation of XML serialization is at the root of the encoding problems Xindice continues to face.
So I feel we should get rid of TextWriter, or implement it as a wrapper over more established XML serializing codebases, like Xerces ( if we can depend on one parser ), or I believe TrAX is supposed to have serializing hooks too.
This is just what I think, what do others think??
I believe the reason this was originally done was just performance and the ability to have an easier way to serialize things. I can't claim to know all the issues, but I definitely prefer to use existing code wherever possible so if the custom serializer can be replaced it's probably a good thing.
Fernando Padilla
Kimbro Staken Java and XML Software, Consulting and Writing http://www.xmldatabases.org/ Apache Xindice native XML database http://xml.apache.org/xindice XML:DB Initiative http://www.xmldb.org
