Re: Making Xerces parse other formats

On Thu, 6 Mar 2003 22:28:30 -0800 Dean Roddey wrote: > I don't think you'd find it worth the effort. The core parser bits are > very heavily tied directly to the XML format. There is no reason for it > to do otherwise really, since it's an XML parser. You could obviously > slip your own parsing sy

RE: Making Xerces parse other formats

I don't think you'd find it worth the effort. The core parser bits are very heavily tied directly to the XML format. There is no reason for it to do otherwise really, since it's an XML parser. You could obviously slip your own parsing system underneath a SAX or DOM API, since they are pretty well s

Making Xerces parse other formats

Hi! I'm working on alternate encodings of XML and one of my objectives is compatibility with XML API and processing. I'd like to have Xerces be able to recognize and parse the alternate format too, so that I may have a working demo available. I'd like to know whether the XML parsing and generatio

Re: DOS attack via Xerces

As of 2.1, you can configure Xerces-C++ to completely ignore the external subset of a DTD when not validating. You can also install an EntityResolver yourself and do that. You could even have a trusted version of the DTD on the server and use that instead of the one specified by the system ID

DOS attack via Xerces

Hi, I saw the following DOS security alert in xerces-j-user newsgroup > -+> > > [EMAIL PROTECTED]| > > .hsbc.Com| > > > > > 12/12/2002 03:37 | > > PM | > > Please respond to| > > xerces-j-user| > > > > -+-

DO NOT REPLY [Bug 17633] - Empty complex type definition is always non-mixed even if declaration says otherwise

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 17633] - Empty complex type definition is always non-mixed even if declaration says otherwise

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

Re: new member

Hi, nice to have you on board :) If you have a bug fix then this is normally attached to a bugzilla bug and the committers apply them as frequently as possible. If you have new code like this then you need to get it to a commiter. I will happily review/commit this code for you. The form

new member

Title: new member Hi All. I am an experienced developer but new to the Xerces project. I have worked extensively on the MSXML DOM parsers. I like the Xerces project very much and would like to contribute actively towards its development. To make a start, I added some code to the DOMCoun

DO NOT REPLY [Bug 3399] - Error in SAXException::getMessage

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug

DO NOT REPLY [Bug 17589] - Refactoring ...

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

RE: The primary document entity could not be opened

I don't set any options. I have a class which inherits from DOMErrorHandler, I only set the error handler to a class of this type. I cut and paste the related section from my classes to a main function and a few functions. here is the code snippet: // Test_Fcs.cpp : Defines the entry point for th

DO NOT REPLY [Bug 17723] New: - Linker error

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

Re: The primary document entity could not be opened

Hi, post a snippet of you code from where you create your parser and set the options. Gareth On Thu, 6 Mar 2003, Williams, Rodger wrote: > I catch following error, in a try&catch statement, on parsing a > string(pulled from a text file) to construct a xerces document: > "An excep

The primary document entity could not be opened

> I catch following error, in a try&catch statement, on parsing a > string(pulled from a text file) to construct a xerces dom document: > "An exception occured! Type:RuntimeException, Message:The primary > document entity could not be opened. > Id=E:\dev\prgm102\<\request>" > Langauge: VC++ 6

The primary document entity could not be opened

I catch following error, in a try&catch statement, on parsing a string(pulled from a text file) to construct a xerces document: "An exception occured! Type:RuntimeException, Message:The primary document entity could not be opened. Id=E:\dev\prgm102\<\request>" Langauge: VC++ 6.0 Xerces Vers

DO NOT REPLY [Bug 13436] - Deprecated standard C++ headers in StdOutFormatTarget.cpp

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu