Base64 validator even more strict?

I've been running into problems with the way data type validation of base64Binary is done forever, but this is hitting critical now. ;-( If I'm understanding correctly, the 2.6.0 changes now require that datatype normalization be on (I note the default is off) in order to get very typical base64 c

Re: Missing xerces-c_2D.lib in xerces-c_2_6_0-windows_nt-msvc_60?

> But the reason for doing this is eloquently expressed > in this very thread--people were confused by this > library's presence, and some thought they needed it > around to use the parser. Are you sure that's what's being expressed? Because that's not how I read it. I read it as "the distribut

RE: Missing xerces-c_2D.lib in xerces-c_2_6_0-windows_nt-msvc_60?

> This was done intentionally. On no other platform were both debug and > release binaries both issued, so it wasn't clear why this was being done > on Windows. No functionality is lost. As David just noted, this is a problem for at least some of us. Is there any chance of reposting the zip fi

Re: Missing xerces-c_2D.lib in xerces-c_2_6_0-windows_nt-msvc_60?

Hi Dave, But the reason for doing this is eloquently expressed in this very thread--people were confused by this library's presence, and some thought they needed it around to use the parser. The expression "you're damned if you do, you're damned if you don't" comes to mind here. :) Fortunate

Re: Missing xerces-c_2D.lib in xerces-c_2_6_0-windows_nt-msvc_60?

> This was done intentionally. On no other platform > were both debug and release binaries both issued, > so it wasn't clear why this was being done on Windows. > No functionality is lost. Actually, functionality is lost, because you can no longer build debug executables for your applications th

Re: Missing xerces-c_2D.lib in xerces-c_2_6_0-windows_nt-msvc_60?

Hi Carolina, This was done intentionally. On no other platform were both debug and release binaries both issued, so it wasn't clear why this was being done on Windows. No functionality is lost. Cheers! Neil Neil Graham Manager, XML Parser Development IBM Toronto Lab Phone: 905-413-3519, T/L

[jira] Commented: (XERCESC-1240) xml:lang attribute is not validated

The following comment has been added to this issue: Author: Scott Cantor Created: Tue, 12 Oct 2004 12:31 PM Body: This is still broken in 2.6.0. Double ugh. - View this comment: http://issues.apache.org/jira/brow

[jira] Resolved: (XERCESC-1213) delete XercesDOMParser object does not release memory under Sun Solaris

Message: The following issue has been resolved as INVALID. Resolver: cargilld Date: Tue, 12 Oct 2004 9:41 AM Marking invalid as per previous comment from Dallas. - View the issue: http://issues.apache.org/jira/bro

[jira] Resolved: (XERCESC-1201) xerces-c-2_3_0 doesn't compile with gcc 2.95 on Linux Debian

Message: The following issue has been resolved as INVALID. Resolver: cargilld Date: Tue, 12 Oct 2004 9:35 AM Closing this issue as it works in the latest code. We don't supply fixes for earlier releases, although a comment has been added to this issue that may resolve the problem.

[jira] Resolved: (XERCESC-1209) Problem with id usage across schema documents

Message: The following issue has been resolved as FIXED. Resolver: cargilld Date: Tue, 12 Oct 2004 9:32 AM Updating resolution to fixed, as Khaled checked in a change a while ago. - View the issue: http://issues.a

[jira] Resolved: (XERCESC-1251) makeContentModel in ComplexTypeInfo could crash Xerces when creating a MixedContentModel

Message: The following issue has been resolved as FIXED. Resolver: cargilld Date: Tue, 12 Oct 2004 9:06 AM Updating resolution to fixed, as Khaled checked in a change a while ago. - View the issue: http://issues.a

[jira] Created: (XERCESC-1286) Escapes memories

Message: A new issue has been created in JIRA. - View the issue: http://issues.apache.org/jira/browse/XERCESC-1286 Here is an overview of the issue: -