RE: Proposal Review: Using C++ Namespace

I read somewhere, thought it was the C++ standard but can't find it now, could have been comp.lang.c++.moderated too, a statement that using-directives are necessary but evil, and that lists of using-declarations are the 'expected' usage, i.e. using XERCES???::XercesDomParser; usin

Re: serializing a DOMDocument with namespaces

> Hi, > I will take a look at what is required to sort out namespaces for > DOMWriter early next week and report back. I do still need this > functionality. Can you post your code once it is done? thx. >I don't think the IBM guys are going to be working on any > more level 3 stuff before Christma

DO NOT REPLY [Bug 13491] - avoid deleting through void* in DOMDocumentImpl.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

DO NOT REPLY [Bug 13435] - Memory mismanagement in DOMDocumentImpl.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

DO NOT REPLY [Bug 14265] - Access violation with Null systemId/publicId in DTDScanner

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 14265] New: - Access violation with Null systemId/publicId in DTDScanner

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: Xerces 2.1.0 RPM for linux

Thomas, Could you please write something on "Build on linux using rpm" which will be part of the "Build Instruction"? thanks. Rgds, PeiYong - Original Message - From: "Thomas Woerner" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: "PeiYong PY Zhang" <[EMAIL PROTECTED]> Sent: T

Re: serializing a DOMDocument with namespaces

Thank you for you quick answer. Gareth Reakes wrote: [EMAIL PROTECTED]"> Hi, you need to use functionality that has not yet been implemented. The DOMWriter should sort out namespaces for you. There is also a method called NormalizeDocument on Node that will do this (again not implemented).

RE: serializing a DOMDocument with namespaces

Hi, before this method changed from NormalizeNS it was fairly high up on my to do list. The scope of the method has now increased significantly. I will take a look at what is required to sort out namespaces for DOMWriter early next week and report back. I do still need this functionalit

RE: serializing a DOMDocument with namespaces

Again are there any plans a proper implementation of NormalizeDocument would be in xerces code in the recent future. I was thinking xerces 2.2 towards the end of the year. Thanks Kiran -Original Message- From: Gareth Reakes To: [EMAIL PROTECTED] Sent: 11/5/02 9:00 AM Subject: Re: serializ

Re: serializing a DOMDocument with namespaces

Hi, you need to use functionality that has not yet been implemented. The DOMWriter should sort out namespaces for you. There is also a method called NormalizeDocument on Node that will do this (again not implemented). I believe I have some quite horrible code lying around somewhere that

serializing a DOMDocument with namespaces

Hello, We are trying to serialize an in-memory DOMDocument with a DOMWriter into a MemBufFormatTarget (Xerces 2.1.0). This used to work fine for the tests, when we didn't use namespaces, but now we do and the resulting string can't be parsed again since the writer doesn't generate the "xmlns" a

DO NOT REPLY [Bug 14260] New: - MacOSUnicodeConverter::upperCase() passes wrong arguments to Carbon function

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

AW: split-cdata-sections does work quite good, but not perfect

PeiYong, sorry for waiting so long with my answer. I was very busy and couldn't get into this issue. Thank you very much for your demo program! It helped me to enable splitting of CDataSections in my application :-) . But I'm still not quite satisfied. Let's suppose, I want to put the following c

How to restrict length on list in schema

Is there a way to specify a length or maxLength on a list in schema? Does the Xerces 2.1 schema capability handle this? Has anyone done this successfully with Xerces 2.1? Thanks, M. Scott Gordon ADSS Software Engineer BAE Systems Mission Solutions Inc. [EMAIL PROTECTED]

RE: Proposal Review: Using C++ Namespace

A namespace is an ID space separator, where an ID can be a type, a variable, or a function [unfortunately not a macro, but hey what can you do]. A using clause short-circuit the whole namespace and exposes all it's IDs into the current namespace. This is namespace cluttering, and is totally agai

Re: OSX: crash in setEncoding() ?

James - I will glady file a bug report as soon as I'm sure it's not my mistake. I believe it's a debugging issue. Maybe gdb just catches a thrown exception that is supposed to be caught by Xerces. (I had the same issue debugging a Xerces based application in BCB on Windows.) How do I turn this b

Re: Problem with startElement and other SAX2 events

Try to use ContentHandler instead of defaultHandler and implement interface handler calls #include class AwdSaxHandler : public ContentHandler { . . . or override the method that you want to catch from AwdSaxHandler. e.g. void AwdSaxHandler::startElement( const XMLCh *uri,