DO NOT REPLY [Bug 12560] - Use const in DOMWriter

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_b

Derived Schema datatypes

Is there any way to get the information regarding the name of the derived schema datatype. Currently if it is integer, I get the datatype names as decimal which is the base type. Is this information retrievable from the DatatypeValidator. Thanks Kiran

Parser pointers, Node pointers, leaks etc

1. Is it necessary to keep XercesDOMParser around or can one just delete it, after retrieving the DOM Document ? or would there be other exceptions/etc somewhere else in the implementation? Of course, one may need to persist to the same file later like myserializer->writeNode(myTarget, *mynode); {

RE: SEnumVal example

Sorry for the distribution. Looks like the sample had an error. Kiran -Original Message- From: Bagepalli, Kiran [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 02, 2002 4:04 PM To: '[EMAIL PROTECTED]' Subject: SEnumVal example I am trying to read an instance document which refers to

SEnumVal example

I am trying to read an instance document which refers to a schema which imports other schemas. I just get an error saying'no output available'. These were picked from an example exercise. Could you please let me know what I am missing and these files cannot be parsed. Thanks Kiran camera.xml

RE: SAX2Count > 3MB when statically linked ????

Please post to the list in plain text rather than HTML (more people will be able to read your email, and thus offer help). No, on UNIX, many linkers fast link the entire static library to an executable creating a larger than neccesary executable. Using the strip command, you can pull out all unr

RE: SAX2Count > 3MB when statically linked ????

Brad, are you asking if I stipped SAX2Count down to meet the simple requirement of just spitting out ERR line so and so vs , Valid doc ? That's all I want. Well, I didn't edit SAX2Count down  for my purposes. I noticed that the size of the xereces DLL had varied a lot between some releases. In one

RE: Serialize and unserialize DOMDocument over socket

Excuse my ignorance. Is the createDocument() method deprecated. I used to write code as DOMDocument* pDOMDocument = m_pImpl->createDocument(); DOMElement* pRootElement = pDOMDocument->createElementNS("www.abc.com", "a:rootNode"); pDOM

RE: SAX2Count > 3MB when statically linked ????

Did you strip the binary? cheers, Brad -Original Message- From: Bill Boggs [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 02, 2002 3:43 PM To: [EMAIL PROTECTED] Subject: SAX2Count > 3MB when statically linked SAX2Count > 3MB when statically linked I'm a newbie ... does

SAX2Count > 3MB when statically linked ????

SAX2Count  > 3MB when statically linked I'm a newbie ... does this make sense ?  Is the API that expansive and does it have that many dependencies within it ? All I'm looking for is any command-line app for validating XML/DTD.  I was going to use SAX2Count.Do you Yahoo!? New DSL Internet Acce

RE: WRONG_DOCUMENT_ERR when appending a DOMDocument to DOMNode

HI, I tried it and it works, thanks. -Original Message- From: Jesse Pelton [mailto:[EMAIL PROTECTED]] Sent: 02/10/2002 02:16 To: '[EMAIL PROTECTED]' Subject: RE: WRONG_DOCUMENT_ERR when appending a DOMDocument to DOMNode You'll probably need to call DOMDocument::importNode(). -Orig

DO NOT REPLY [Bug 13065] - Versioning macros defined incorrectly

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_b

DO NOT REPLY [Bug 13065] - Versioning macros defined incorrectly

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_b

RE: WRONG_DOCUMENT_ERR when appending a DOMDocument to DOMNode

You'll probably need to call DOMDocument::importNode(). -Original Message- From: Justin Kirby [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 02, 2002 2:13 PM To: [EMAIL PROTECTED] Subject: Re: WRONG_DOCUMENT_ERR when appending a DOMDocument to DOMNode All you have to do is create a

Re: WRONG_DOCUMENT_ERR when appending a DOMDocument to DOMNode

All you have to do is create a docfragment and append the document to that. Then add the docfragment to the root of the other document... DOMDocument *one = . DOMDocument *two = . DOMDocumentFragment *frag = two->createDocumentFragment(); frag->appendChild(two->getDocumentElement()); DO

DO NOT REPLY [Bug 13065] - Versioning macros defined incorrectly

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_b

RE: Serialize and unserialize DOMDocument over socket

Thank you. I have tried this and it WORKS. -dh -Original Message- From: Gareth Reakes [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 02, 2002 12:26 PM To: [EMAIL PROTECTED] Subject: RE: Serialize and unserialize DOMDocument over socket Hi, If you just pass in 0 for the ur

WRONG_DOCUMENT_ERR when appending a DOMDocument to DOMNode

Hi, I am trying to append a DOMDocument to a root node in another document.When i do that, i get WRONG_DOCUMENT_ERR: I read that DOMDocumentFragment must be used in such situation, is that correct.If so can anyone show me how to do that. Thanks, Rama -

RE: Serialize and unserialize DOMDocument over socket

Hi, Thanks I will try that. -dh -Original Message- From: Gareth Reakes [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 02, 2002 12:26 PM To: [EMAIL PROTECTED] Subject: RE: Serialize and unserialize DOMDocument over socket Hi, If you just pass in 0 for the uri bit of the cr

RE: Serialize and unserialize DOMDocument over socket

Hi, If you just pass in 0 for the uri bit of the create methods tehn it should all work. It does for me. Gareth On Wed, 2 Oct 2002, Dave Hoffer wrote: > Hi, > > I sort of understand what you are saying. > > For my application, I do not think I need namespaces. I only added them

DO NOT REPLY [Bug 13213] New: - DOMImplementation::hasFeature() should be const

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_b

RE: Serialize and unserialize DOMDocument over socket

Hi, I sort of understand what you are saying. For my application, I do not think I need namespaces. I only added them to solve the localName problem. Yes, WSZ_NAMESPACE_URI is not null because, again I thought I had to add this to solve the localName problem. All I am trying to do is take s

RE: Serialize and unserialize DOMDocument over socket

Hi, I completely forgot about this problem as I replaced your ns info with nulls. Sorry about that. I assume that WSZ_NAMESPACE_URI is not null. If this is the case then when you serialize it you will lose the namespace information. When you parse it again the elements will have a diffe

RE: Serialize and unserialize DOMDocument over socket

Hi Gareth, Right you are. I have fixed this...the new code is below. However, I have the same problem, the namespaceURI's do not match (one is null). bool IMessage::FillMsg() { DOMImplementation* impl = DOMImplementationRegistry::getDOMImplementation(L"Core"); m_pDomDocumen

A survey about handling bugs in open source projects

Hello all Xerces-C contributors, I am conducting a survey about the way defects (or bugs-I use these two words interchangeably) are handled in open source software projects. It is very easy to fill out. It consists of three short sections which can be completed at once or in different sessions.

RE: Serialize and unserialize DOMDocument over socket

Hi, comment below On Wed, 2 Oct 2002, Dave Hoffer wrote: > Here is the code... > > bool IMessage::FillMsg() > { > DOMImplementation* impl = >DOMImplementationRegistry::getDOMImplementation(L"Core"); > > m_pDomDocument = impl->createDocument( >

RE: Serialize and unserialize DOMDocument over socket

Here is the code... bool IMessage::FillMsg() { DOMImplementation* impl = DOMImplementationRegistry::getDOMImplementation(L"Core"); m_pDomDocument = impl->createDocument( WSZ_NAMESPACE_URI,// root element namespace URI.

RE: Serialize and unserialize DOMDocument over socket

Hi, post you document creation stuff (the stuff in FillDoc) and Ill have a look. Gareth On Wed, 2 Oct 2002, Dave Hoffer wrote: > Hi, > > Thank you for the replies. I did what you said, this HAS FIXED the localName issue. > Thank you very much. However, the very next test in the i

RE: Serialize and unserialize DOMDocument over socket

Hi, Thank you for the replies. I did what you said, this HAS FIXED the localName issue. Thank you very much. However, the very next test in the isEqualNode code is a check of getNamespaceURI()'s. This fails. What seems to be happening is that the object that we create from the byte strea

DO NOT REPLY [Bug 13065] - Versioning macros defined incorrectly

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_b

RE: Serialize and unserialize DOMDocument over socket

Hi, thank you. I will try what you have told me. thank you very much. -dh -Original Message- From: Gareth Reakes [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 02, 2002 8:30 AM To: [EMAIL PROTECTED] Subject: RE: Serialize and unserialize DOMDocument over socket Hi, The

RE: Serialize and unserialize DOMDocument over socket

Hi, The problem is 2 fold. First you have not set the namespaces feature on DOMBuilder to true - do that like this: pDOMBuilder->setFeature(X("namespaces"), true); secondly you are mixing level 1 and level 2 creation methods. createDocument uses level 2 (createElementNS) and th

DO NOT REPLY [Bug 13199] New: - problem cloning DOMDocument

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_b

DO NOT REPLY [Bug 12369] - invalid output from DOMWriter using MemBufFormatTarget

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_b

DO NOT REPLY [Bug 13197] New: - problem deleting attributes when element is released

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_b

DO NOT REPLY [Bug 13192] - core dump of SAXCount and SAX2Count

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_b

Re: Decode CDATASection Content

Hi Gareth, thanks again. Bug#11534 actually _is_ contained in Xerces 2.1.0. But anyway some bug fix on the way to the latest Xerces version (30 Sept) has solved the problem. I get the desired output using the latest version. Martin > I think Ive got to the bottom of our confusion

Re: XInclude

Hi, xinclude is not part of the DOM specifications so it is not supported in xerces-c. Gareth On Wed, 2 Oct 2002, Martin Ilkerl wrote: > Hi, it's me again! > > One week ago I asked following question: > > Actually I'm working with Xerces 2.1 and with schemas. > > The xml-document I

DO NOT REPLY [Bug 13192] New: - core dump of SAXCount and SAX2Count

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_b

DO NOT REPLY [Bug 13191] - Multiple xsd:imports on the same namespace

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_b

DO NOT REPLY [Bug 13191] New: - Multiple xsd:imports on the same namespace

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_b