XSD validation gives closed stream.

[sham]

Hi to all,

I have a memory Stream that is validated using the XmlValidatingReader
object. My stream is passed to the XmlValidatingReader object together with
the xsd file. This works fine.

Once validated (and there are no errors), I want to use the same stream in
other piece of functionality. As soon as I access this stream I get the
error "System.objectDispose exception. Cannot access a closed stream". I get
the same error if I used a fileStream (in this case I get cannot access a
closed file error). I tried stream.seek(0,0) before accessing it but I then
get the same error at the seek line.

Any clues on what the problem is?

Sham.

[Martin Honnen]

sham wrote:

I have a memory Stream that is validated using the XmlValidatingReader
object. My stream is passed to the XmlValidatingReader object together with
the xsd file. This works fine.

Once validated (and there are no errors), I want to use the same stream in
other piece of functionality. As soon as I access this stream I get the
error "System.objectDispose exception. Cannot access a closed stream". I get
the same error if I used a fileStream (in this case I get cannot access a
closed file error). I tried stream.seek(0,0) before accessing it but I then
get the same error at the seek line.

Any clues on what the problem is?

With .NET 2.0 you can use XmlReaderSettings with CloseInput set to false
<http://msdn2.microsoft.com/en-us/library/system.xml.xmlreadersettings.closeinput.aspx>
XmlValidatingReader also has a property Settings so you can use e.g.
XmlValidatingReaderInstance.Settings.CloseInput = false
--

Martin Honnen --- MVP XML
http://JavaScript.FAQTs.com/

[John Saunders]

"sham" <sh******@inspirationmatters.comwrote in message
news:eD**************@TK2MSFTNGP06.phx.gbl...

Hi to all,

I have a memory Stream that is validated using the XmlValidatingReader
object. My stream is passed to the XmlValidatingReader object together
with the xsd file. This works fine.

Once validated (and there are no errors), I want to use the same stream in
other piece of functionality. As soon as I access this stream I get the
error "System.objectDispose exception. Cannot access a closed stream". I
get the same error if I used a fileStream (in this case I get cannot
access a closed file error). I tried stream.seek(0,0) before accessing it
but I then get the same error at the seek line.

Any clues on what the problem is?

Yes. You closed the stream.

Did you use the stream inside of a using block?

John

[sham]

I am currently using .net 1.1
What are my options to not close the stream? (apart from creating another
stream).

No I am not using a using block. It looks as thought the xmlValidatingReader
is closing the stream.

Sham.

"John Saunders" <john.saunders at trizetto.comwrote in message
news:%2****************@TK2MSFTNGP02.phx.gbl...

"sham" <sh******@inspirationmatters.comwrote in message
news:eD**************@TK2MSFTNGP06.phx.gbl...

>Hi to all,

I have a memory Stream that is validated using the XmlValidatingReader
object. My stream is passed to the XmlValidatingReader object together
with the xsd file. This works fine.

Once validated (and there are no errors), I want to use the same stream
in other piece of functionality. As soon as I access this stream I get
the error "System.objectDispose exception. Cannot access a closed
stream". I get the same error if I used a fileStream (in this case I get
cannot access a closed file error). I tried stream.seek(0,0) before
accessing it but I then get the same error at the seek line.

Any clues on what the problem is?

Yes. You closed the stream.

Did you use the stream inside of a using block?

John

[Martin Honnen]

sham wrote:

I am currently using .net 1.1
What are my options to not close the stream? (apart from creating another
stream).

No I am not using a using block. It looks as thought the xmlValidatingReader
is closing the stream.

Yes, it is documented
<http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemXmlXmlValidatingReaderClassCloseTopic.a sp>
that "If this reader was constructed using a stream, this method also
calls Close on the underlying stream."
It looks as if the only way is not calling the Close method on the
XmlValidatingReader until you know you do not longer need the memory
stream. On the other hand that does sound like a good idea in general to
not close the reader when you are finished with it.

--

Martin Honnen --- MVP XML
http://JavaScript.FAQTs.com/