Hi Alberto,
Thanks for this. I've tried it out and it looks good.
One quick question, have you had any success in running the tests? I've
been trying out DOMTest and DOMMemTest, both have seg faults. Looking
closer at DOMTest, the fault occurs in libstdc++.a after attempting to
throw an excep
Hi Brian,
At 09.34 03/02/2005 +, Brian Reynolds wrote:
Hi Alberto,
Thanks for this. I've tried it out and it looks good.
One quick question, have you had any success in running the tests? I've
been trying out DOMTest and DOMMemTest, both have seg faults. Looking
closer at DOMTest, the fault o
hi all,
our xerces crashes while parsing with schema.
we use xerces c++ version 2.5
the problem:
our xml-file contains coordinates like
1.1,1.1 2.2,2.2 3.3,3.3
with different number of coordinates within the tag
It should be a repetition of with blanks/tabs/returns
Hi,
You could try patch from http://issues.apache.org/jira/browse/XERCESC-1242
As I can see the problem is similar.
Good luck !
Weber, Claus. wrote:
hi all,
our xerces crashes while parsing with schema.
we use xerces c++ version 2.5
the problem:
our xml-file contains coordinates like
1.1,1.1 2
Hi All,
In reviewing some recent appends and Jira bugs I would like to get some
feedback before making the following changes:
(1) Change compiler options for Linux and MSVC++ to generate more warning
messages. By regularly monitoring the regular builds of
xercesc we can try and have war
+1
Gareth
On 2 Feb 2005, at 20:43, David Cargill wrote:
Hi All,
I propose that we invite Vitaly Prapirny to become a Xerces-c
committer.
He has been with the project
for sometime now and produced a number of patches as well as forum
responses. Committers please
respond with your vote. Thanks.
Hey,
All sound good to me.
Gareth
On 3 Feb 2005, at 10:59, David Cargill wrote:
Hi All,
In reviewing some recent appends and Jira bugs I would like to get some
feedback before making the following changes:
(1) Change compiler options for Linux and MSVC++ to generate more
warning
message
At 15.43 02/02/2005 -0500, David Cargill wrote:
Hi All,
I propose that we invite Vitaly Prapirny to become a Xerces-c committer.
He has been with the project
for sometime now and produced a number of patches as well as forum
responses. Committers please respond with your vote. Thanks.
Here is my
[
http://issues.apache.org/jira/browse/XERCESC-1325?page=comments#action_58551 ]
Alberto Massari commented on XERCESC-1325:
--
Alexander,
the current version in CVS should cope with the /Zc:wchar_t compiler switch.
Can you check it, and add a co
Hi David,
At 05.59 03/02/2005 -0500, David Cargill wrote:
Hi All,
In reviewing some recent appends and Jira bugs I would like to get some
feedback before making the following changes:
(1) Change compiler options for Linux and MSVC++ to generate more warning
messages. By regularly monitoring the re
Xerces C++ defines an encoding-string that Xerces/Java refuses to parse
---
Key: XERCESC-1336
URL: http://issues.apache.org/jira/browse/XERCESC-1336
Project: Xerces-C++
Type: Bug
Versions: 2.6.0
Makes sense to me, except for one detail: I think names specified in
standards should specifically be exempted from the proposed Mixed Case
guideline. Such names should match the casing used in the standard.
To meet this guideline without such an exemption, names such as node
types, filter action
Title: 0x1A Character
Hi All,
I have a question regarding an Invalid XML character and Xerces behavior pertaining to it. Apologize since my questions are not completely Xerces specific.
Recently, we found out that some of our XML text nodes contain the 0x1A character. This causes the Xer
Title: 0x1A Character
The spec is hard to read on this point. So-called
"restricted" characters are not allowed. See the
discussion beginning at http://www.stylusstudio.com/xmldev/200410/post30210.html for
an explanation.
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Sent: Thu
Hello,
I'm having problems using XercesDOMParser to parse a document with the
following prolog:
I set up the parser, call parse, and I end up with an exception:
xercesc_2_4::MalformedURLException.
My set up code:
static XercesDOMParser::ValSchemesgValScheme =
XercesDOMParser::V
"file:///c:/template/TestCaseReport_V1.0.dtd" should work (note the
additional forward slash). At least, this format works for locating
schemas specified in an element's schemaLocation in Xerces 2.5.
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]
> Sent: Thur
On Thu, Feb 03, 2005 at 07:39:27AM -0700, [EMAIL PROTECTED] wrote:
> Recently, we found out that some of our XML text nodes contain the 0x1A
> character. This causes the Xerces parser to throw a Invalid character
> (Unicode: 0x1A) error.
>
> Upon investigating the XML specs, the XML 1.0 Spec doe
DOMMemTest fails with Segmentation violation(xserces1.7 + ICU transcode +
windows2000)
Key: XERCESC-1337
URL: http://issues.apache.org/jira/browse/XERCESC-1337
Project: Xerces-C++
[
http://issues.apache.org/jira/browse/XERCESC-1337?page=comments#action_58588 ]
Leon Zhang commented on XERCESC-1337:
-
Environment should be:
windows2000 + xseces 1.7(/2.5) + ICU transcode
> DOMMemTest fails with Segmentation violation(xserces1.
[
http://issues.apache.org/jira/browse/XERCESC-1337?page=comments#action_58590 ]
Leon Zhang commented on XERCESC-1337:
-
Normally, whole testcase carsh right after "// Attr01 " of "// Attr02"
blocks.
Since after trancode is changed to WIN32, no c
20 matches
Mail list logo
