You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@xerces.apache.org by bu...@apache.org on 2004/07/24 02:17:05 UTC
DO NOT REPLY [Bug 27450] -
Validating against schemas importing other schemas
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=27450>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=27450
Validating against schemas importing other schemas
------- Additional Comments From jzheng@mail.arc.nasa.gov 2004-07-24 00:17 -------
Hi Frank, Khaled
I'm new to Xerces and I'm still playing with DOMPrint. I tried to validate and
parse an xml with some pretty complicated schema. I got the same message Frank
got. I read through your bug reports and comments, but I still don't quite
understand how you got around the problem. I see that I need to
setXMLEntityResolver with a user supplied entity resolver. But I don't have one,
and I have no idea how to make one or what to include. Do you have an example?
Thanks.
Jian
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
Re: v1.7.0 and VS.NET 2003
Posted by Vitaly Prapirny <ma...@mebius.net>.
Markus wrote:
> That would be ideal, yes. But:
> going from 1.7.0 to 2.0.0 is already difficult.
> We get a lot of "cannot instantiate abstract class"
> errors. And DOMString seems to be removed
> completely from 2.0.0.
You can find old DOM API (with DOMString) in
src\xercesc\dom\deprecated (but it is deprecated
so it would be better to try the new API).
> Also, do we need to build xerceslib in VS.NET
> for using it with our app? So far we've used
> the binaries from xerces distribution but those
> are built using MSVC6 as I understand it. Right?
Absolutely.
Good luck !
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
Re: v1.7.0 and VS.NET 2003
Posted by Markus <ma...@mail.student.oulu.fi>.
That would be ideal, yes. But:
going from 1.7.0 to 2.0.0 is already difficult.
We get a lot of "cannot instantiate abstract class"
errors. And DOMString seems to be removed
completely from 2.0.0.
Also, do we need to build xerceslib in VS.NET
for using it with our app? So far we've used
the binaries from xerces distribution but those
are built using MSVC6 as I understand it. Right?
Markus
----- Original Message -----
> Hi,
> Markus wrote:
> > 1. Upgrade xerces? To which version?
> The latter one (2.5.0) is better :)
> And use XMLString::release instead of delete[].
>
> Good luck !
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
> For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
Re: v1.7.0 and VS.NET 2003
Posted by Vitaly Prapirny <ma...@mebius.net>.
Hi,
Markus wrote:
> 1. Upgrade xerces? To which version?
The latter one (2.5.0) is better :)
And use XMLString::release instead of delete[].
Good luck !
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
v1.7.0 and VS.NET 2003
Posted by Markus <ma...@mail.student.oulu.fi>.
Hello,
I have succesfully used code bits like
XMLCh* xmlChAttrName = XMLString::transcode( "Name" );
// process the string...
delete [] xmlChAttrName;
with v1.7.0 in MSVC6 environment.
But now that we've moved to VS.NET 2003 it
crashes on pretty much every call to delete [].
Reading the FAQ I guess the problem occurs because
my app and xerces don't use the same runtime library
anymore.Right?
So, what are my choices to resolve this issue?
1. Upgrade xerces? To which version?
2. Build v1.7.0 with VS.NET? Don't have the
project files to do so....
Markus
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org