Hi Joe,

>Imports aren't involved in this case (it's the trivial "personnel" example
that ships with Xerces as a sample of >schema use), and I'm loading the
same file that the sample document specified via
>xsi:noNamespaceSchemaLocation. This Should Be Working, right?

Should be working now--but until quite recently there was a bug such that
schemas without namespaces weren't handled properly by grammar caching.  So
do a CVS update and see what happens...

>>If you don't want to use the schema component API

>I'd be glad to. I don't know how to; as you've agreed, there really isn't
a cookbook for components and
>configurations yet, and reverse-engineering existing code convinces me
that there are interactions I really
>don't understand yet. Which is why I'm looking for guidance...! <grin/>

Just talked to Sandy--this isn't quite ready for prime-time yet.  So you're
best bet is to rely on XMLSchemaLoader magic for now...

>I'll try that. Same GRAMMAR_POOL property name, I assume? Seems a bit odd
that I have to both bind
>them this way _and_ explicitly put the loaded grammar into the pool... or
does this make the latter step
>unnecessary?

Yeah, this obviates the need for the latter step.

As I think Elena's pointed out before, we have no solution for this
question of validation-within-specific-context.

>Another complication: There's some argument about whether xsi:type and
xsi:schemaLocation directives in >the fragment should be honored (long
story, still being argued, don't ask). I presume there's no way to tell
>the schema validator to ignore them and use only the preloaded grammars,
and I'm honestly not sure
>whether there should be.

There's definitely nothing to be done about xsi:type attributes.  You could
try registering your own entity resolver to handle schemaLocations; if your
resolver resolved to a schema with an appropriate targetNamespace and no
decls, you might have an effective "ignore".  You could probably generate
such a schema programmatically as well; an ugly kludge though.  Lots of
open
issues here, no doubt...

Cheers,
Neil
Neil Graham
XML Parser Development
IBM Toronto Lab
Phone:  905-413-3519, T/L 969-3519
E-mail:  [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to