> There has been a demand for annotation support which is ignored > after validation. I have few comments regarding your proposed > solution. You are storing references to the appinfo/documentation > dom nodes. First, this means that you are keeping around the whole > dom tree in memory. Second, once the schema is processed, it's > dom tree representation is no longer available in memory (it's deleted). > I think the solution would be to follow the same mechanism as the > SchemaElementDecl class. Create a SchemaAnnotation, > SchemaAppinfo and SchemaDocumentation classes that would be > created and filled by TraverseSchema as it's processing the > corresponding dom nodes.
Took the words right out of my pine window :) Richard, I will mail you what I have from the last implementation (I believe from Peter) that I think Khaled will be more happy with. Regarding the tests, take a look in the tests directory off of XERCESCROOT. I don't immediately see a directory in there that would be suitable, but you will see there are many different ways we tests depending on the situation. Gareth -- Gareth Reakes, Head of Product Development +44-1865-203192 DecisionSoft Limited http://www.decisionsoft.com XML Development and Services --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
