Bob,
This should be same as whatever currently supported in Xerces-J, i.e., the
answer should be yes. The traverseInclude method of TraverseSchema will
call the user's EntityResolver with the value of the schemaLocation
attribute. The user's EntityResolver can then replace it with whatever they
like to redirect the location.
Tinny
Bob Kline wrote:
> On Mon, 9 Apr 2001, Tinny Ng wrote:
>
> > Just wanna to give you an update on our Schema Development progress.
> > Khaled Noaman, Pei Yong Zhang, and I have been working hard in the
> > past couple of months to port the Schema Support in Xerces-J to
> > Xerces-C, and everything is still on track right now. We have
> > finished the plumbing fundamental work (like Exception handling,
> > Schema messaging, Content model, Schema element decl/attribute decl
> > ... etc.), and are now moving on to Schema specific items:
> >
> > 1. Schema Validator
> > 2. Datatype Validator
> > 3. Traverse Schema
>
> Hi, Tinny. Could we get a sneak preview into one of the features? Will
> it be possible to plug in a resolver for the <include> element so we can
> (for example) pull an included schema document out of a database instead
> of having the parser expect to find everything in the file system?
>
> --
> Bob Kline
> mailto:[EMAIL PROTECTED]
> http://www.rksystems.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
