Problem with ISAXXMLReader

[Developer]

CoInitialize(NULL);
ISAXXMLReaderPtr pReader = NULL;

CHR(pReader.CreateInstance(__uuidof(SAXXMLReader)) );

A1ContentHandler * pA1ContentHandler = A1ContentHandler::CreateInstance();
CHR(pReader->putContentHandler(pA1ContentHandler));
SaxErrorHandlerBase * pErrHndlr = new SaxErrorHandlerBase();
CHR(pReader->putErrorHandler(pErrHndlr));

CHR(pReader->putFeature(L"exhaustive-errors", VARIANT_TRUE));
------------------------------------------------------------------------
CHR is a macro to check the return value of the function.
pReader->putFeature() returns 80070057.

What am I doing wrong?
Thanks.
CB

[Steven Cheng[MSFT]]

Hi CB,

As for the error you get on calling the "putFeature" method of the
SaxXmlReader, I've also done some tests on my side and also encountered the
problem. I've done the test in both C++ AND VB and try most of the feature
keys listed in the following reference:

#SAX Reader Features
http://msdn.microsoft.com/library/de...us/xmlsdk/html
/sax_reader_features.asp

And it seems that some of them always return the "InvalidArg" error (just
the 80070057 you mentioned).
I'm not sure whether this is the document's error or there is anything else
concerned with the setting. Currently I'm consulting some further experts
and will let you know if there is any new findings. Thanks for your
understanding.
Regards,

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

Get Preview at ASP.NET whidbey
http://msdn.microsoft.com/asp.net/whidbey/default.aspx

[Developer]

I just found in the MSDN Library that ISAXXMLReader::putFeature(), called
with "exhaustive-errrors" or "schema-validation", returns E_FAIL.
What does that mean? That those features can't be set?
If you can set "schema-validation", what sort of sense does it make to
return E_FAIL? And if something goes wrong, how could you tell?

"Steven Cheng[MSFT]" <v-******@online.microsoft.com> wrote in message
news:mq*************@cpmsftngxa10.phx.gbl...

Hi CB,

As for the error you get on calling the "putFeature" method of the
SaxXmlReader, I've also done some tests on my side and also encountered the problem. I've done the test in both C++ AND VB and try most of the feature
keys listed in the following reference:

#SAX Reader Features
http://msdn.microsoft.com/library/de...us/xmlsdk/html /sax_reader_features.asp

And it seems that some of them always return the "InvalidArg" error (just
the 80070057 you mentioned).
I'm not sure whether this is the document's error or there is anything else concerned with the setting. Currently I'm consulting some further experts
and will let you know if there is any new findings. Thanks for your
understanding.
Regards,

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

Get Preview at ASP.NET whidbey
http://msdn.microsoft.com/asp.net/whidbey/default.aspx

[Steven Cheng[MSFT]]

Hi CB,

Thanks for your followup. As for the ISAXXMLReader and SAXXMLReader's
putFeatures, I've also checked the documentations (online MSDN and local)
and done some tests on my side. It seems that the documentation has some
problems on the description. In the document, it said that those features
such as

exhaustive-errors
external-general-entities
external-parameter-entities
namespaces
namespace-prefixes
parameter-entities
preserve-system-identifiers
prohibit-dtd
schema-validation
server-http-request

#putFeature Method
http://msdn.microsoft.com/library/de...us/xmlsdk/html
/isaxxmlreader_interface.asp

Requires MSXML3 OR later version. But my test show that the
"exhaustive-errors" feature is only supported by MSXML 4 and above. So
we'd change the code as :

HRESULT hr = CoCreateInstance(__uuidof(SAXXMLReader40),
NULL,
CLSCTX_ALL,
__uuidof(ISAXXMLReader),
(void **)&pRdr);

Thanks.

Regards,

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

Get Preview at ASP.NET whidbey
http://msdn.microsoft.com/asp.net/whidbey/default.aspx

[Developer]

Thanks, Steven, it seems to be working with msxml 4.

"Steven Cheng[MSFT]" <v-******@online.microsoft.com> wrote in message
news:$R**************@cpmsftngxa06.phx.gbl...

Requires MSXML3 OR later version. But my test show that the
"exhaustive-errors" feature is only supported by MSXML 4 and above. So
we'd change the code as :

HRESULT hr = CoCreateInstance(__uuidof(SAXXMLReader40),
NULL,
CLSCTX_ALL,
__uuidof(ISAXXMLReader),
(void **)&pRdr);