XmlValidatingReader and xs:import support

[Nathan Alden]

Hi all. I have an XML schema that has a couple of <xs:import> tags that
reference (using schemaLocation) schemas as embedded resources in a DLL. For
example:

<xs:import namespace=http://www.my.com/my.xsd
schemaLocation="res://assembly/?MyAssembly,MyAssembly.my.xsd"/>

I've attached a derived XmlResolver class called XmlResourceResolver to the
XmlTextReader that is reading this schema. I've loaded the schema itself
from an embedded resource just fine using the custom resolver. The problem
is it appears as though the resolver is not being called to resolve the
<xs:import> element. This is, of course, leading to a whole mess of "element
not declared" errors later on in the schema.

I read a post over at .NET 247 where a Microsoft support rep stated that a
problem appearing to be the same as this one is indeed a bug with .NET 1.1.
I was wondering if anyone else had either gotten this to successfully work
or is aware of exactly what the bug is.

Thanks,

Nate

[Zafar Abbas]

Did you attach the resolver to the reader or schema collection?

"Nathan Alden" <[e-mail]> wrote in message
news:OK**************@TK2MSFTNGP14.phx.gbl...

Hi all. I have an XML schema that has a couple of <xs:import> tags that
reference (using schemaLocation) schemas as embedded resources in a DLL. For example:

<xs:import namespace=http://www.my.com/my.xsd
schemaLocation="res://assembly/?MyAssembly,MyAssembly.my.xsd"/>

I've attached a derived XmlResolver class called XmlResourceResolver to the XmlTextReader that is reading this schema. I've loaded the schema itself
from an embedded resource just fine using the custom resolver. The problem
is it appears as though the resolver is not being called to resolve the
<xs:import> element. This is, of course, leading to a whole mess of "element not declared" errors later on in the schema.

I read a post over at .NET 247 where a Microsoft support rep stated that a
problem appearing to be the same as this one is indeed a bug with .NET 1.1. I was wondering if anyone else had either gotten this to successfully work
or is aware of exactly what the bug is.

Thanks,

Nate

[Nathan Alden]

As I stated in my post, I attached the resolver to the XmlTextReader object
I used to read the schema.

"Zafar Abbas" <so*****@somewhere.com> wrote in message
news:O7**************@TK2MSFTNGP12.phx.gbl...

Did you attach the resolver to the reader or schema collection?

"Nathan Alden" <[e-mail]> wrote in message
news:OK**************@TK2MSFTNGP14.phx.gbl...

Hi all. I have an XML schema that has a couple of <xs:import> tags that
reference (using schemaLocation) schemas as embedded resources in a DLL.

For

example:

<xs:import namespace=http://www.my.com/my.xsd
schemaLocation="res://assembly/?MyAssembly,MyAssembly.my.xsd"/>

I've attached a derived XmlResolver class called XmlResourceResolver to

the

XmlTextReader that is reading this schema. I've loaded the schema itself
from an embedded resource just fine using the custom resolver. The
problem
is it appears as though the resolver is not being called to resolve the
<xs:import> element. This is, of course, leading to a whole mess of

"element

not declared" errors later on in the schema.

I read a post over at .NET 247 where a Microsoft support rep stated that
a
problem appearing to be the same as this one is indeed a bug with .NET

1.1.

I was wondering if anyone else had either gotten this to successfully
work
or is aware of exactly what the bug is.

Thanks,

Nate

[Zafar Abbas]

You need to pass the resolver to the Compile method of XmlSchema. Attaching
a resolve to the XmlTextReader will not work since reading in the schema
does not resolve imports.

Zafar

"Nathan Alden" <vi***************@hotmail.com> wrote in message
news:ed*************@TK2MSFTNGP10.phx.gbl...

As I stated in my post, I attached the resolver to the XmlTextReader object I used to read the schema.

"Zafar Abbas" <so*****@somewhere.com> wrote in message
news:O7**************@TK2MSFTNGP12.phx.gbl...

Did you attach the resolver to the reader or schema collection?

"Nathan Alden" <[e-mail]> wrote in message
news:OK**************@TK2MSFTNGP14.phx.gbl...

Hi all. I have an XML schema that has a couple of <xs:import> tags that
reference (using schemaLocation) schemas as embedded resources in a DLL.

For

example:

<xs:import namespace=http://www.my.com/my.xsd
schemaLocation="res://assembly/?MyAssembly,MyAssembly.my.xsd"/>

I've attached a derived XmlResolver class called XmlResourceResolver to

the

XmlTextReader that is reading this schema. I've loaded the schema

itself from an embedded resource just fine using the custom resolver. The
problem
is it appears as though the resolver is not being called to resolve the
<xs:import> element. This is, of course, leading to a whole mess of

"element

not declared" errors later on in the schema.

I read a post over at .NET 247 where a Microsoft support rep stated that a
problem appearing to be the same as this one is indeed a bug with .NET

1.1.

I was wondering if anyone else had either gotten this to successfully
work
or is aware of exactly what the bug is.

Thanks,

Nate