Problem on Intel Solaris

Hello, I have a problem using the XML library on Solaris Intel: bash$ uname -a SunOS jptky502 5.7 Generic_106542-15 i86pc i386 i86pc The XML library gives a core when exception occures. I don't know how exactly but the stack is corrupted. In the util/XMLException.hpp there is the code: #define

Re: [ANN]: Xerces-C 2.3.0 released!

DOMDocument appears to have lost the methods canSet/set/getNormalizationFeature, but they are still in the documentation. Could someone please comment. -- Colin Paul Adams Preston Lancashire - To unsubscribe, e-mail: [EMAIL PROT

DO NOT REPLY [Bug 20287] - [RFC 2396]: URI has no scheme if ':' occurs after '?' or '#'.

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 20287] New: - [RFC 2396]: URI has no scheme if ':' occurs after '?' or '#'.

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 20005] - [RFC 2396]: Scheme specific part cannot be empty.

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: [ANN]: Xerces-C 2.3.0 released!

Can someone comment on the level of DOM 3 normalization support. What is lacking from what is recommended in the spec. Thanks Kiran -Original Message- From: Neil Graham [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 27, 2003 3:03 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECT

Found Error after porting

Hi again, I did some more testing on my OS/2 port of Version 2.2.0. After running DOMCount.exe i get the following error: Fatal Error at file D:\Projekte\xml-xerces\os2-binary\bin\test.xml, line 3, char 9 Message: Expected comment or processing instruction The content of the file is very simp

DO NOT REPLY [Bug 20006] - [RFC 2396]: Authority is not restricted to 255 characters.

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 20006] - [RFC 2396]: Authority is not restricted to 255 characters.

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 memory manager alignment issues?

Hi Michael, Thanks for your feedback. For many of the committers (certainly for me!), this was a first experience implementing a pluggable memory management scheme; so it's useful to know about the possible pitfalls about the approach that we've taken. Among other things, you state in your e-mai

Re: How to commit updated port for OS/2

Hi Joachim, As you can see, Xerces 2.3.0 just came out. :) In general, we need patches/fixes to the code base to be made against what is currently in CVS rather than against a particular stable release; as you'll no doubt see when you upgrade, there were a fair number of changes between 2.2 and

[ANN]: Xerces-C 2.3.0 released!

Hi all, The Xerces-C team is pleased to announce that Xerces-C 2.3.0 is now available. The primary features of this release are: - pluggable memory management: Allows an application to have Xerces request memory from a user-supplied object rather than directly from the heap. To allow for maxim

RE: Yet another XMLString::release question

I guess this is more of a C++ question As of now, the delete may not be a prob. But by invoking delete [] you are assuming that a new [] was used to allocate your string. May make your code incompatible with other transcoders / versions of xerces etc... -Vinayak > -Original Message--

Yet another XMLString::release question

Is there any advantage to calling release over simply calling delete? For example: char *pMsg = XMLString::transcode(m_Node->getNodeValue()); XMLString::release(&pMsg); versus char *pMsg = XMLString::transcode(m_Node->getNodeValue()); delete []pMsg;

How to commit updated port for OS/2

Hi all, this is my first mail to this mailing list and I hope I'm at the right place. Today I've finished the porting of Xerces-C 2.2.0 to OS/2. I've edited all the necessary files within the Projects/OS2/VACPP directory and made a complete binary distribution. Furthermore I've edited "OS2Platf

Re: [PATCH]: Small typo in dom/deprecated/AttrImpl

Hi Michael, Thanks for pointing this out. I'm less certain that this isn't relevant; the original code was quite explicit about nulling the DOMString stored in value.str, and that's why I (tried to) take pains to keep doing so. But at worst this will cause a small memory leak; it's better than

[PATCH]: Small typo in dom/deprecated/AttrImpl

Hi everyone, I noticed a small typo in AttrImpl ('==' instead of '='). It shouldn't make a difference behaviourly because it looks like DOMString's destructor reduces the ref count of fHandle if not done explicitly. Index: xml-xerces/c/src/xercesc/dom/deprecated/AttrImpl.cpp =