Hi Shakya, I understand what Mukul is saying, but disagree that Xerces is working correctly. He described a work around for that specific case, not a general solution.
I believe users should be able to provide an array of schema documents to SchemaFactory.newInstance() which all have the same namespace and that Xerces should be fixed so that it can process that. It should be possible for the SchemaFactory implementation to internally generate a synthetic schema document which combines the user's list of schema documents together. From the schema loader's perspective this would look like one master schema document for the namespace which has includes to all the others. Taking that a step further, another schema document could be generated which glues all the namespaces together with imports. Thanks. Michael Glavassevich XML Technologies and WAS Development IBM Toronto Lab E-mail: [email protected] E-mail: [email protected] Shakya Wijerama <[email protected]> wrote on 02/20/2012 12:56:37 AM: > Hello Michael, > > I was looking at the JIRA issue you have given [1]. According to the > comment Mukul has mentioned, it is not a bug, because when the > "schema1.xsd" is loaded "schema2.xsd" is resolved since the latter > file is already included in the "schema1.xsd". I am not sure whether > I should continue working on this and hope your opinion. > > Thanks. > > [1]. https://issues.apache.org/jira/browse/XERCESJ-1130 > > Regards, > > Shakya Wijerama > > Senior Student, > Faculty of Applied Sciences, > Sabaragamuwa University of Sri Lanka.
