Daniel Barclay wrote: > XML Schema specification says (part 1, section 4.2.1): > > Note: The above is carefully worded so that multiple <include>ing > of the same schema document will not constitute a violation of clause > 2 of Schema Properties Correct (�3.15.6), but applications are allowed, > indeed encouraged, to avoid <include>ing the same schema document more > than once to forestall the necessity of establishing identity component > by component. > > Although that is only a note, it clearly refers to the concept of the > "same schema document."
JaxMeXS is unable to "establish identity component by component". You might consider that as a lack of an important feature, but that's how it is. If you volunteer for adding that feature, you are welcome. As long as that is missing, you've got to make sure, that the parser knows, that it is including the "same schema document". Currently, this is done by ensuring that the system ID is *the same*. Not the same as in "the same file in the filesystem" or as in "referring to the same URL", but lexically the same. Again, if you don't like this as it is, you are welcome to volunteer for a better solution. However, unlike as in the case of the Javadocs, I clearly reserve the rights to carefully review and possible refuse such changes. You might be able to convice another developer, of course, or even a majority. Believe it or not, but what is currently in the code is sufficient to achieve what you want, if you are ready to add an EntityResolver and make sure, that *the lexically same* system ID's are given to the parser. Jochen --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
