General Question about validation

Hi, I want to understand in details the difference between validation levels for Xerces C++ parser - IDOMParser::Val_Auto; IDOMParser::Val_Always; I checked the API Documentation, but could not satisfy myself. Please point me to the links / references. Thanks, Shirish __

Question about DOMErrorHandler

I have not been able to get the DOMErrorHandler interface to return any information. Even while using the DOMPrint example with the schema and intentionally submitting non-valid code, the error is always returned through the DOMTreeErrorReporter (ErrorHandler). I thought the DOMErrorHandler was s

Weird linker errors

Hi, i'm using BCB 5 pro, and I'm getting the following errors. __ Do you Yahoo!? Yahoo! Tax Center - forms, calculators, tips, more http://taxes.yahoo.com/[Linker Error] Unresolved external 'DOMImplementationRegistry::getDOMImplementation(const wcha

DO NOT REPLY [Bug 17516] - Thread safety problems in .../util/ and ../util/regx

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 17516] - Thread safety problems in .../util/ and ../util/regx

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: wchar_t and XMLCh

Believe me, wchar_t is evil. Redefine your own 16 bits string or use a string instead, which you can convert to/from XMLCh* easily. Even if theoretically unsigned short is not necessarily two bytes long, it is far more reliable than wchar_t being 2 bytes long. Best -Message d'origine- D

RE: wchar_t and XMLCh

> Thanks for your suggestion. That will probably work in every case except this one. > The reason being we are building a wrapper library over Xerces and our interface > exposes only std::wstring. We don't expose internal xerces types. In particular > on Solaris, we want to link against STLport

RE: wchar_t and XMLCh

David, Thanks for your suggestion. That will probably work in every case except this one. The reason being we are building a wrapper library over Xerces and our interface exposes only std::wstring. We don't expose internal xerces types. In particular on Solaris, we want to link against STLport

Re: wchar_t and XMLCh

> Basically I need to convert the XMLCh* to a std::wstring and vice versa. In Xerces, XMLCh is > typdef-ed to unsigned short (2 bytes). Under win32, there is no need for conversion since wchar_t > is also typedef-ed to unsigned short. In Solaris/Linux/VMS, however, wchar_t is typedef-ed to > un

Re: wchar_t and XMLCh

I changed, and it works for me. However I use SAX only. -Kosta - Original Message - From: qchen To: [EMAIL PROTECTED] Sent: Tuesday, March 04, 2003 5:43 PM Subject: wchar_t and XMLCh I know this question has probably been discussed before, but I just want

wchar_t and XMLCh

I know this question has probably been discussed before, but I just want to see if there are any new solutions.   Basically I need to convert the XMLCh* to a std::wstring and vice versa. In Xerces, XMLCh is typdef-ed to unsigned short (2 bytes). Under win32, there is no need for conversion

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

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

DO NOT REPLY [Bug 17633] New: - 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: create static library?

Hi, create something like: cd $XERCESCROOT/lib ar -cq xerces.a ../obj/LINUX/*.o Gareth On Mon, 3 Mar 2003, Brice Ruth wrote: > Good afternoon, list members. > > I am working on a project that I hope to use xercesc in (and am well on > my way to doing so). I just determined that the

Re: DOCTYPE node

Hi, I will an attempt to answer your question (I think I'm right). You do need a DOCTYPE unless you set up an EntityResolver to use this automatically. In this case none of the XML files need use a DOCTYPE. Gareth On Mon, 3 Mar 2003, Raghu Nandan wrote: > Folks: > > When parsing multip

RE: DOCTYPE node

Yes the doctype must be specified in the XML file to be able to be loaded by a validating parser. It is XML standard. Regards Erik Rydgren Mandarinen systems AB Sweden -Original Message- From: Raghu Nandan [mailto:[EMAIL PROTECTED] Sent: den 3 mars 2003 22:23 To: [EMAIL PROTECTED] Subje