About the spaces in filenames problem, I wonder about it too but mostly use
UNIX so it hasn't come up yet.
I wonder if anybody knows what to do about that. Also, with the setProperty
call, convert that path to UTF-16 or you will have problems! Here's a C++
function that will take care of it.
That's all I know how to help you with for now.
HTH!
Matt
// widen function
// Converts ASCII std::string to XMLCh array.
// NOTE: Caller must delete XMLCh array when finished with it.
XMLCh* widen(const string& src)
{
// Allocate buffer.
XMLCh* dest = new XMLCh[src.length() + 1];
// Copy from string to buffer.
string::size_type i;
for (i=0; i < src.length(); ++i)
dest[i]=(XMLCh)src[i];
// Add NULL byte.
dest[i+1]=0;
// Return const pointer to array.
return dest;
}
-----Original Message-----
From: Elisha Berns [mailto:[EMAIL PROTECTED]
Sent: Sunday, May 22, 2005 6:41 PM
To: Xerces C++ Development
Subject: Handling of schemaLocation attribute
Does the handling of schemaLocation have a bug or a feature in Xerces
2.6?
The schemaLocation attribute whose value syntax is pairs of namespace
names/xsd file locations only works correctly when there are no space
characters in the xsd file location. Is this a bug or a feature?
Under Win32 I can't predict or count on when the full path to the xsd
filename will have space characters so something seems broken here.
I experimented with adding either single or double quotes around the
full path to the xsd file, but that doesn't work either.
What am I missing about how to use schemaLocation and also:
reader.setProperty(XMLUni::fgXercesSchemaExternalSchemaLocation, (
void*)strLocation.c_str());
works the same way.
Thanks,
Elisha Berns
[EMAIL PROTECTED]
tel. (310) 556 - 8332
fax (310) 556 - 2839
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
___________________________________________________________________
The information contained in this message and any attachment may be
proprietary, confidential, and privileged or subject to the work
product doctrine and thus protected from disclosure. If the reader
of this message is not the intended recipient, or an employee or
agent responsible for delivering this message to the intended
recipient, you are hereby notified that any dissemination,
distribution or copying of this communication is strictly prohibited.
If you have received this communication in error, please notify me
immediately by replying to this message and deleting it and all
copies and backups thereof. Thank you.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
