Glen Daniels wrote: > > Rough in the beginnings of dynamic schema support. For now, the only > real functionality is getting the "null" QName. > > Introduce the SchemaVersion class, which is associated with > MessageContexts and SerializationContexts and provides version- > specific schema constants and behavior. > > The implicit assumption here is that for a given piece of processing > (a single request), only one schema version will be active. (We make > this same assumption about SOAP versions)
As I read the code, it appears that the check for null is made against all compiled in schema versions, not merely the active one? For future growth and scalability, I like the idea of having only one single active version. - Sam Ruby
