Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-1264
Here is an overview of the issue:
-
The following comment has been added to this issue:
Author: Scott Cantor
Created: Tue, 28 Sep 2004 2:41 PM
Body:
Mixed news.
The good news is, I think the problem I was reporting is fixed, and I can validate an
anyType'd element that contains arbitrary XML attributes.
The bad ne
The following comment has been added to this issue:
Author: Khaled Noaman
Created: Tue, 28 Sep 2004 4:37 PM
Body:
Would you please try the latest code? The following schema and sample worked fine.
http://www.w3.org/2001/XMLSchema";>
The following comment has been added to this issue:
Author: Khaled Noaman
Created: Tue, 28 Sep 2004 5:11 PM
Body:
Fix is in CVS. Would you please try the latest code?
-
View this comment:
http://issues.apache.org
The following comment has been added to this issue:
Author: Scott Cantor
Created: Wed, 29 Sep 2004 8:56 AM
Body:
Latest cvs checked, looks like it's working correctly now. My testing isn't rigorous,
just a few basic test cases I've been using, but I don't see any unexpected result
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-1207
Here is an overview of the issue:
-
Message:
The following issue has been resolved as FIXED.
Resolver: PeiYong Zhang
Date: Wed, 29 Sep 2004 12:39 PM
Dan Rosen's patch applied and available in cvs.
-
View the issue:
http://issues.apache.org/jira/brow
The following comment has been added to this issue:
Author: Khaled Noaman
Created: Wed, 29 Sep 2004 2:11 PM
Body:
Fix is in CVS. Would you please verify?
-
View this comment:
http://issues.apache.org/jira/browse/
Message:
The following issue has been resolved as FIXED.
Resolver: cargilld
Date: Wed, 29 Sep 2004 2:50 PM
Fix is in CVS. Would you please verify?
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-121
The following comment has been added to this issue:
Author: Dee
Created: Wed, 29 Sep 2004 11:18 PM
Body:
Hi All,
Does anyone have any advice/suggestion as to what could be the best possible approach
to solve this leak..
Thanks
The following comment has been added to this issue:
Author: Dee
Created: Wed, 29 Sep 2004 11:30 PM
Body:
Hi,
i also tried using this snippet ..but the memory leak is still there..
std::string GetXmlStringNew(DOMNode *pNode)
{
std::string sXML = "";
try
{
DOMImplementation*
Message:
A new issue has been created in JIRA.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-1279
Here is an overview of the issue:
-
Message:
A new issue has been created in JIRA.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-1280
Here is an overview of the issue:
-
The following issue has been updated:
Updater: Vitaly Prapirny (mailto:[EMAIL PROTECTED])
Date: Thu, 30 Sep 2004 12:56 AM
Comment:
Patch against xml-xerces_20040929043320.tar.gz snapshot.
Changes:
Attachment changed to xercesc-snapshot-20040929043320-borland.patch.
Message:
The following issue has been closed.
Resolver: Alberto Massari
Date: Thu, 30 Sep 2004 3:30 AM
I guess this was just a test...
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-1278
Here is a
Message:
A new issue has been created in JIRA.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-1281
Here is an overview of the issue:
-
The following issue has been updated:
Updater: Alberto Massari (mailto:[EMAIL PROTECTED])
Date: Thu, 30 Sep 2004 3:54 AM
Comment:
The XML file
Changes:
Attachment changed to rT.xml
-
For a full
The following issue has been updated:
Updater: Alberto Massari (mailto:[EMAIL PROTECTED])
Date: Thu, 30 Sep 2004 3:54 AM
Comment:
The XMLSchema file
Changes:
Attachment changed to restrictionTest.xsd
--
The following comment has been added to this issue:
Author: Alberto Massari
Created: Thu, 30 Sep 2004 3:55 AM
Body:
Note: both Xerces-J and SQC find the schema valid
-
View this comment:
http://issues.apache.org/
Message:
The following issue has been resolved as FIXED.
Resolver: Alberto Massari
Date: Thu, 30 Sep 2004 4:02 AM
Fix is in CVS
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-538
Here is an overvi
Message:
The following issue has been resolved as FIXED.
Resolver: Alberto Massari
Date: Thu, 30 Sep 2004 6:17 AM
I have checked in your changes; instead of leaving the .cpp files with no content I
have chosen to remove them.
Please verify.
Alberto
---
Message:
The following issue has been closed.
Resolver: PeiYong Zhang
Date: Thu, 30 Sep 2004 7:05 AM
Oded,
Your patch is in cvs, please help verify, thanks.
Rgds,
PeiYong
-
View the issue:
http://issues.apac
The following comment has been added to this issue:
Author: PeiYong Zhang
Created: Thu, 30 Sep 2004 8:51 AM
Body:
Dee,
To isolate the leakage problem, I've done test on the sample, DOMPrint and there is
no leakage reported from Purify.
You may start from DOMPrint as well, b
The following comment has been added to this issue:
Author: George Aggrey
Created: Thu, 30 Sep 2004 11:42 PM
Body:
Authors is not in the schema so validation should fail but it doesn't.
Here is my command line:
domprint -v=always -n -f -s instance.xml
The following comment has been added to this issue:
Author: Alberto Massari
Created: Fri, 1 Oct 2004 1:18 AM
Body:
I have done the suggested changes; can you verify them again?
Thanks,
Alberto
-
View this comment:
The following comment has been added to this issue:
Author: cargilld
Created: Fri, 1 Oct 2004 5:56 AM
Body:
Hi George,
I just tried it out using the latest source and got:
Error at file "d:\bugs\1282.xml", line 4, column 16
Message: Unknown element 'x:authors'
Error at file "d:\
The following comment has been added to this issue:
Author: Vitaly Prapirny
Created: Fri, 1 Oct 2004 6:05 AM
Body:
You forgot to change DeprecatedDOMCount.mak, so DeprecatedDOMCount.cpp from
Projects\Win32\BCC.551\Xerces-all\DeprecatedDOMCount not used by make and we have
linker
The following comment has been added to this issue:
Author: Vitaly Prapirny
Created: Fri, 1 Oct 2004 6:17 AM
Body:
In previous comment I mean revertion of PATHCPP to it's previous value:
PATHCPP = .;
-
View this c
The following comment has been added to this issue:
Author: Alberto Massari
Created: Fri, 1 Oct 2004 7:17 AM
Body:
:-(
Please try again.
Alberto
-
View this comment:
http://issues.apache.org/jira/browse/XERCES
The following comment has been added to this issue:
Author: Vitaly Prapirny
Created: Fri, 1 Oct 2004 12:14 PM
Body:
Verified,
Thanks
-
View this comment:
http://issues.apache.org/jira/browse/XERCESC-1280?page=com
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-1280
Here is an overview of the issue:
-
The following comment has been added to this issue:
Author: George Aggrey
Created: Sat, 2 Oct 2004 12:12 AM
Body:
Hello David,
DOMPrint from xml-xerces_20041002043233.tar.gz correctly validates the xml file above.
I probably mixed something up. I guess the remaining issue is that
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-1197
Here is an overview of the issue:
-
The following issue has been updated:
Updater: Alberto Massari (mailto:[EMAIL PROTECTED])
Date: Mon, 4 Oct 2004 12:49 AM
Changes:
assignee changed from Xerces-C Developers Mailing List
type changed from Bug to New Feature
description changed fr
Message:
The following issue has been closed.
Resolver: Alberto Massari
Date: Mon, 4 Oct 2004 2:05 AM
Duplicate of #866; actually, the 32 namespace limit the bug is referring is related to
the start/end of a namespace scope, so it will be hit in an XML file with more than N
levels
Message:
The following issue has been resolved as FIXED.
Resolver: Alberto Massari
Date: Mon, 4 Oct 2004 2:28 AM
A fix is in CVS. Please verify.
Alberto
-
View the issue:
http://issues.apache.org/jira/browse/XERC
The following issue has been updated:
Updater: Alberto Massari (mailto:[EMAIL PROTECTED])
Date: Mon, 4 Oct 2004 2:29 AM
Changes:
description changed from I receive the following error when attempting to
parse a file with
a deep nesting of elements (MathML). This file v
The following issue has been updated:
Updater: Alberto Massari (mailto:[EMAIL PROTECTED])
Date: Mon, 4 Oct 2004 2:31 AM
Comment:
It looks like that editing an issue raises the priority to "blocker"...
Changes:
priority changed from Blocker to Major
-
Message:
The following issue has been closed.
Resolver: Alberto Massari
Date: Mon, 4 Oct 2004 2:44 AM
Duplicate of #1264
Alberto
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-548
Here is an over
Message:
The following issue has been closed.
Resolver: Alberto Massari
Date: Mon, 4 Oct 2004 2:55 AM
The storage model for setUserData has changed, and the bug doesn't apply anymore
-
View the issue:
http://issue
Message:
The following issue has been closed.
Resolver: Alberto Massari
Date: Mon, 4 Oct 2004 3:06 AM
Duplicate of #1267
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-386
Here is an overview of t
The following issue has been updated:
Updater: Alberto Massari (mailto:[EMAIL PROTECTED])
Date: Mon, 4 Oct 2004 3:14 AM
Changes:
assignee changed from Xerces-C Developers Mailing List
description changed from Regarding IXMLDOMDocument...
If a document is s
The following issue has been updated:
Updater: Alberto Massari (mailto:[EMAIL PROTECTED])
Date: Mon, 4 Oct 2004 3:16 AM
Changes:
assignee changed from Xerces-C Developers Mailing List
description changed from The Xerces COM wrapper (xerces-com) should be a
Message:
The following issue has been resolved as FIXED.
Resolver: Alberto Massari
Date: Mon, 4 Oct 2004 3:27 AM
In 2.6, that line has been removed
Alberto
-
View the issue:
http://issues.apache.org/jira/browse/X
The following issue has been updated:
Updater: Alberto Massari (mailto:[EMAIL PROTECTED])
Date: Mon, 4 Oct 2004 3:28 AM
Changes:
assignee changed from Xerces-C Developers Mailing List
description changed from I got the following error during compilation
Uni
The following issue has been updated:
Updater: Alberto Massari (mailto:[EMAIL PROTECTED])
Date: Mon, 4 Oct 2004 3:29 AM
Changes:
assignee changed from Xerces-C Developers Mailing List
description changed from On HP-UX 10.20 using CC, a template repository
Message:
The following issue has been closed.
Resolver: Alberto Massari
Date: Mon, 4 Oct 2004 3:33 AM
Duplicate of #1279.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-1273
Here is an overview o
The following issue has been updated:
Updater: Alberto Massari (mailto:[EMAIL PROTECTED])
Date: Mon, 4 Oct 2004 3:34 AM
Changes:
Component changed to Build
Component changed from Utilities
Component changed from Validating Parser (DTD)
The following issue has been updated:
Updater: Alberto Massari (mailto:[EMAIL PROTECTED])
Date: Mon, 4 Oct 2004 4:31 AM
Changes:
Component changed to Non-Validating Parser
Component changed from Build
Message:
A new issue has been created in JIRA.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-1283
Here is an overview of the issue:
-
Message:
A new issue has been created in JIRA.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-1284
Here is an overview of the issue:
-
The following issue has been updated:
Updater: Daniel McLean (mailto:[EMAIL PROTECTED])
Date: Mon, 4 Oct 2004 11:56 PM
Comment:
Here is the testcase demonstrating the problems described.
Changes:
Attachment changed to MemParseEncoding.tar.gz
The following comment has been added to this issue:
Author: PeiYong Zhang
Created: Tue, 5 Oct 2004 8:42 AM
Body:
Dominik,
Do you have a patch for the bug? If not, would you please
post the code to show the bug?
The code shall
1. have the string containing the 0x0e
Message:
A new issue has been created in JIRA.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-1285
Here is an overview of the issue:
-
The following issue has been updated:
Updater: Daniel McLean (mailto:[EMAIL PROTECTED])
Date: Thu, 7 Oct 2004 9:31 PM
Comment:
The same problem appears to occur when explicitly setting an encoding
of "UTF-8" when a BOM occurs at the start of the UTF-8 XML entity
(which is allowed).
Message:
A new issue has been created in JIRA.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-1290
Here is an overview of the issue:
-
The following comment has been added to this issue:
Author: Alberto Massari
Created: Mon, 18 Oct 2004 9:17 AM
Body:
The error you are seeing is signaling that a buffer overrun has happened (in debug
mode every allocated buffer is terminated with a specific byte sequence that is
c
Message:
A new issue has been created in JIRA.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-1291
Here is an overview of the issue:
-
The following issue has been updated:
Updater: Michael McMaster (mailto:[EMAIL PROTECTED])
Date: Tue, 19 Oct 2004 1:28 AM
Comment:
Solution.
Changes:
Attachment changed to DOMString.patch
-
For
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-1247
Here is an overview of the issue:
-
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-1237
Here is an overview of the issue:
-
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-1193
Here is an overview of the issue:
-
Message:
The following issue has been closed.
Resolver: PeiYong Zhang
Date: Tue, 19 Oct 2004 8:32 AM
Private ctor/dtor is meant for Singleton.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-1075
H
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-979
Here is an overview of the issue:
-
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-831
Here is an overview of the issue:
-
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-748
Here is an overview of the issue:
-
Message:
The following issue has been closed.
Resolver: PeiYong Zhang
Date: Tue, 19 Oct 2004 8:51 AM
using SAX may solve this problem since DOM is known memory thirsty..
-
View the issue:
http://issues.apache.org/
Message:
The following issue has been closed.
Resolver: PeiYong Zhang
Date: Tue, 19 Oct 2004 8:59 AM
BinInputStream derives from XMomory and when it gets deleted, the allocator is
retrieved and used to deallcate memory.
--
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-688
Here is an overview of the issue:
-
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-650
Here is an overview of the issue:
-
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-640
Here is an overview of the issue:
-
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-494
Here is an overview of the issue:
-
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-465
Here is an overview of the issue:
-
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-452
Here is an overview of the issue:
-
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-424
Here is an overview of the issue:
-
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-416
Here is an overview of the issue:
-
The following comment has been added to this issue:
Author: PeiYong Zhang
Created: Tue, 19 Oct 2004 9:56 AM
Body:
Valerio,
As the community becomes more and more concerned about the license and copyright
issues related to code contribution, we would be more than happy to check
The following comment has been added to this issue:
Author: PeiYong Zhang
Created: Tue, 19 Oct 2004 9:58 AM
Body:
Vladimir,
As the community becomes more and more concerned about the
license and copyright issues related to code contribution,
we would be more th
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-397
Here is an overview of the issue:
-
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-378
Here is an overview of the issue:
-
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-371
Here is an overview of the issue:
-
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-355
Here is an overview of the issue:
-
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-313
Here is an overview of the issue:
-
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-312
Here is an overview of the issue:
-
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-301
Here is an overview of the issue:
-
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-299
Here is an overview of the issue:
-
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-292
Here is an overview of the issue:
-
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-291
Here is an overview of the issue:
-
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-259
Here is an overview of the issue:
-
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-254
Here is an overview of the issue:
-
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-253
Here is an overview of the issue:
-
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-239
Here is an overview of the issue:
-
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-224
Here is an overview of the issue:
-
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-197
Here is an overview of the issue:
-
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-194
Here is an overview of the issue:
-
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-179
Here is an overview of the issue:
-
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-178
Here is an overview of the issue:
-
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-171
Here is an overview of the issue:
-
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-150
Here is an overview of the issue:
-
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-90
Here is an overview of the issue:
-
201 - 300 of 306 matches
Mail list logo
