When parsing a document with a Schema, the DocumentType node was always returned as null. While this was not a big concern, users asked that the document type node never be null. So now this is fixed and the document type node is always created.
When parsing a document with a Schema, the DocumentType node
was always returned as null. While this was not a big concern,
users asked that the document type node never be null. So now
this is fixed and the document type node is always created.

Having done this fix, I realized that we have a larger problem.
Default attribute values are stored in the DocumentTypeImpl
class in ElementDefinition objects. Schema documents are not
currently populating these values. Therefore, default attribute
values don't work in DOM documents that have an associated XML
Schema.

But this problem is compounded by the fact that XML Schema
allows element types to be defined locally. These locally
declared elements can have attributes with default values
so the entire default attribute value implementation in the
DOM would have to be rethought.

This is definitely a REVISIT!


git-svn-id: 21df804813e9d3638e43477f308dd0be51e5f30f@315783 13f79535-47bb-0310-9956-ffa450edef68

RackerWilliams/xercesj,RackerWilliams/xercesj,jimma/xerces,jimma/xerces,jimma/xerces,ronsigal/xerces,RackerWilliams/xercesj,ronsigal/xerces,ronsigal/xerces