Hi Stephen,
the fact that you are getting an "Unknown feature" error means that you
are calling setFeature; but the fgXercesSchemaExternalSchemaLocation
should be set using setProperty (setFeature can turn on or off,
setProperty specifies actual data as value)
Alberto
Stephen Collyer wrote:
Jason Stewart wrote:
Hey Stephen,
On 2/10/08, Stephen Collyer <[EMAIL PROTECTED]> wrote:
I am seeing Xerces throw SAXNotRecognizedException when I
try to set XMLUni::fgXercesSchemaExternalSchemaLocation in both
Win32 and Linux and Xerces 2.7 and 2.8
Is this feature not, in fact, supported ?
I've only got the 3.0 code in front of me and it *is* supported in
SAX2XMLReaderImpl.cpp::setProperty(). It shouldn't make a difference
under Linux or Windows.
I just check viewcvs at:
http://svn.apache.org/viewvc/xerces/c/tags/Xerces-C_2_7_0/src/xercesc/parsers/SAX2XMLReaderImpl.cpp?revision=289502&view=markup
and it looks like the code hasn't changed since 2.7.0, so it should
work there as well.
Right. It appears to be in there.
Maybe I'll let Alberto or someone else comment. Are you doing this
through the C++ API or through the Perl API?
Both, in fact. I'm porting some Perl code that used the Xerces-p
2.7.0 interface, and that exhibited the same problem. However,
at the time, I assumed that it was a limitation in the Perl wrapper.
I'm now porting the code to C++, and I'm seeing the same thing,
with both 2.7 and 2.8. The following code:
catch (XERCES_CPP_NAMESPACE_QUALIFIER SAXNotRecognizedException& e)
{
std::cout << XERCES_CPP_NAMESPACE_QUALIFIER XMLString::transcode(e.getMessage()) << std::endl;
}
emits "Unknown Feature".
