It seems JaxMeXS can't handle schema files that recursively include each other (e.g., A.xsd includes B.xsd, B.xsd includes A.xsd). JaxMeXS hangs in an endless recursion, reading A, then reading B, then reading another copy of A, then reading another copy of B, etc.
I've see this with JaxMe 0.3.1. Does JaxMe 0.4beta still have the same problem? The attached files constitute a small test case.
(Whether or not recursive includes are legal in XML Schema, JaxMeXS should not get stuck in an endless loop. If they are legal, obvioulys JaxMeXS should handle them. If they are not illegal, JaxMeXS still should not hang and, ideally (if JaxMeXS were meant to be a schema checker), should report the error.
It seems that JaxMeXS should keep track of which schema documents it has already read in, and, when processing xsd:include constructs, should check whether the document to be included has already been read in.)
Daniel
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"; > <xsd:include schemaLocation="RecursiveIndirectly1.xsd" /> </xsd:schema>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"; > <xsd:include schemaLocation="RecursiveIndirectly2.xsd" /> </xsd:schema>
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
