[
http://issues.apache.org/jira/browse/XERCESC-1403?page=comments#action_62358 ]
Jesse Pelton commented on XERCESC-1403:
---
Whether or not you use such a macro doesn't matter; what's important is whether
it's defined. What happe
What feature is Xerces missing? According to
http://www.w3.org/TR/2001/NOTE-wsdl-20010315, "WSDL is an XML format,"
so Xerces should be able to parse well-formed WSDL documents. Of
course, it won't understand the semantics of such documents, nor should
it, as a general-purpose XML parser. This s
I can say definitively that at least one person uses the API
documentation (me). Since I didn't raise the accessibility issue, I'll
bet there's at least one other person who uses it. I've never had any
use for the collaboration diagrams.
> -Original Message-
> From: David Cargill [mailt
I used a hexdump utility to examine the contents of your file. It's
UTF-16 with a byte-order mark (BOM). The BOM enables a parser to
determine the encoding and byte order without reference to the declared
encoding. (With a 16-bit encoding, you have to know whether the
high-order byte comes first
What do you mean when you say the file is written in Unicode? UTF-8 is
one of the three standard Unicode encodings (the other two being UTF-16
and UTF-32). Does the encoding specified in the document match the
actual encoding? It might be helpful for you to send a sample document
(as an attachme
I'd agree if this were a violation of am specification, but
it's not. If you have read the thread I referred to, you know
that pretty-printing is only loosely specified. This means, in essence, that
implementations can do whatever they like - there is no right or wrong. You can
certainly pro
There's a thread in the mailing list archive that may be relevant. See
http://marc.theaimsgroup.com/?l=xerces-c-dev&m=111047624410742&w=2.
> -Original Message-
> From: Lumir Vanek [mailto:[EMAIL PROTECTED]
> Sent: Sunday, March 27, 2005 3:04 PM
> To: xerces-c-dev@xml.apache.org
> Subject
Check the archives for my response to your previous message
(http://marc.theaimsgroup.com/?l=xerces-c-dev&m=111047624410742&w=2).
> -Original Message-
> From: Petar Obradovic [mailto:[EMAIL PROTECTED]
> Sent: Thursday, March 10, 2005 1:25 AM
> To: xerces-c-dev@xml.apache.org
> Subject: D
[
http://issues.apache.org/jira/browse/XERCESC-1371?page=comments#action_60427 ]
Jesse Pelton commented on XERCESC-1371:
---
Verified. Thanks, Alby!
> DOMWriter fails to emit default namespace under some circumstan
[ http://issues.apache.org/jira/browse/XERCESC-1371?page=history ]
Jesse Pelton updated XERCESC-1371:
--
Attachment: CreateDOMDocument.cpp
> DOMWriter fails to emit default namespace under some circumstan
Versions: 2.5.0, 2.6.0
Environment: Visual Studio .NET 2003 on Windows XP
Reporter: Jesse Pelton
Attachments: CreateDOMDocument.cpp
I've modified the CreateDOMDocument sample to use createElementNS() rather than
createElement() to create and serialize a document like the foll
You could presumably do this by implementing your own
MemoryManager and specifying it when you call createDocument(),
createDOMBuilder(), or whatever you use to create the document. I believe
that your implementation can manage memory in whatever manner it sees fit,
including releasing memor
Assuming you've created a DOMWriter pointed to by
pWriter:
if (pWriter->canSetFeature(XMLUni::fgDOMXMLDeclaration, false))
pWriter->setFeature(XMLUni::fgDOMXMLDeclaration, false);
From: Shawn Delaney
[mailto:[EMAIL PROTECTED] Sent: Wednesday, February 16, 2005
10:12 PMTo: xer
S... and i'm the one that was
assigned (by HP) to do it...
as
far as i know, no one else has attempted, or entered any (similar) OVMS
bugs... i spent almost a whole day reading the archives looking for anything
similar before i sent this...
-Original Message-From:
I can't provide any assistance myself, but I note that
someone filed a related bug in Jira (http://issues.apache.org/jira/browse/XERCESC-1310)
a couple of months back. You might attach a comment to the bug or contact the
reporter directly to see what progress, if any, has been made. Maybe he'
I think you'll need to download and build the source. Go to
http://xml.apache.org/xerces-c/download.cgi and click the mirror link in
the second paragraph. (You can select another mirror farther down the
page.) You'll probably want xerces-c-src_2_6_0.tar.gz. Then go back to
the Xerces download p
Wow. This is an ambitious proposal. As a user, it sounds wonderful,
including the build infrastructure cleanup. (I don't use the current
system, but posts to the list over the years have made it clear that
it's problematic for many people.) I don't know how long it might take
to accomplish it a
In your shoes, I'd fire up a debugger and see where the problem occurs.
But first, I'd modify my code to check the returns from functions that
return pointers to be sure they're valid before using them. For
instance, parser->getDocument() can return NULL. If it does, you'll
certainly crash when y
First, note that there is no v.5.0. I assume you mean
2.5.0.
1. I doubt Xerces has an ECCN (Export Control Classifcation
Number). I am not a lawyer, but I'd hazard a guess that it falls under
EAR99.
2. Xerces has no cryptographic functionality, whether
related to signatures or encryption
Take a look at the DOMPrint or SAX2Print sample app
(depending on whether you want to build a DOM tree or process your elements in a
stream). With the appropriate options (like "-n -s -f -v=always" for DOMPrint,
"-f -v=always" for SAX2Print), they do full validation against whatever schemas
"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
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
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
[
http://issues.apache.org/jira/browse/XERCESC-1331?page=comments#action_58434 ]
Jesse Pelton commented on XERCESC-1331:
---
Another alternative is to make the variables static class members. I didn't
mention it earlier because I assumed ther
[
http://issues.apache.org/jira/browse/XERCESC-1331?page=comments#action_58425 ]
Jesse Pelton commented on XERCESC-1331:
---
Why is an unnamed namespace better? My understanding is that this is precisely
what external static declarations have
: Win32, Visual Studio .NET 2003, static library
Reporter: Jesse Pelton
Priority: Minor
util/NetAccessors/WinSock/BinHTTPURLInputStream.cpp declares and uses several
global variables. These variables do not appear to be intended to be visible
outside the module. If this is the case, they
I think that's correct. Non-validating parsers are allowed to process
external entities; they're just not required to. As the XML spec
(http://www.w3.org/TR/2004/REC-xml-20040204/#safe-behavior) makes clear,
the behavior of different non-validating parser implementations is less
predictable than
am [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 26, 2005 9:06 AMTo: Jesse
Pelton; xerces-c-dev@xml.apache.org; [EMAIL PROTECTED] Decisionsoft.
ComSubject: AW: XML Document parsing.
Hello,
I
edited the .xml file using an editor and got rid of all the whitespace &
newlin
Title: XML Document parsing.
The text may be whitespace, often used for
formatting for human readability. Unless you tell the parser what whitespace is
significant (via a DTD, for instance), it must retain it
all.
text
is not the same as
text
The former has a newline and s
[
http://issues.apache.org/jira/browse/XERCESC-1327?page=comments#action_57852 ]
Jesse Pelton commented on XERCESC-1327:
---
Case matters, for (at least) three reasons. First, it's easier for a user to
determine that the identifier used b
[
http://issues.apache.org/jira/browse/XERCESC-1327?page=comments#action_57850 ]
Jesse Pelton commented on XERCESC-1327:
---
It looks to me like some enums are all caps and some are mixed case. Every
uppercase enumeration in Xerces 2.5 that I
Bug 1148 (http://issues.apache.org/jira/browse/XERCESC-1148) includes a
patch to make a precursor to Xerces 2.5.0 build under UnixWare 7.1.1. I
don't know if the patch got applied, or if 2.6.0 builds as-is, but I
suspect not, since the bug is still open. If that's the case, you could
try applying
I use a single Xerces binary on various NT generations (NT, 2000, XP).
I happen to build it myself, but that's only because 1) I'm a control
freak and 2) I need static libraries.
> -Original Message-
> From: Tina Kerchner [mailto:[EMAIL PROTECTED]
> Sent: Thursday, December 16, 2004 3:19
Xerces implements standards. If you can get the W3C XML
committee to incorporate this into the standard, I'm sure Xerces will support
it. However, the fact that it's not already there suggests that it might not, in
fact, be "welcome by all."
From: Gill, Prabhprit (Prabh)
[mailto:[
Can you be more specific? For instance, have you tried building and running
the sample applications?
> -Original Message-
> From: Estanislau Puhl [mailto:[EMAIL PROTECTED]
> Sent: Friday, November 19, 2004 1:16 PM
> To: [EMAIL PROTECTED]
> Subject: Xerces and Borlan Builder
>
> Hi,
>
Nor does it seem likely that such a change will be made to the official
code. Xerces implements standards, which makes it predictable and
relatively easy to maintain. If such non-standard behavior is a
requirement, I think you'll have to make your own modifications.
> -Original Message-
>
My understanding is that Intel's 64-bit architecture is
different from AMD's. It would not surprise me at all to learn that Intel's
compiler cannot generate code for AMD chips. Do you know whether it can? If not,
you may need to consider GCC.
From: Lakkundi, Vijayendra R
[mailto:[
[ http://nagoya.apache.org/jira/browse/XERCESC-1297?page=comments#action_54972 ]
Jesse Pelton commented on XERCESC-1297:
---
I'll reiterate what I said on the mailing list yesterday. That's really the correct
place to discuss this, since t
I think you're on to something when you inspect the
document contents. However, I'd consider three changes to make the process
more robust, and there are a couple of simple command-line tests you can run to
try to discover whether your input is being altered before your program sees it.
(I t
Unless you've built a static library, you'll need the DLL at runtime.
It sounds like the library you're linking against is an import library,
which is just a collection of stub routines, not the actual Xerces code.
I think the process of building a static library for Windows has been
discussed bef
If I understand what you're after, the requested behavior
would break compliance with the XML specification. See http://www.w3.org/TR/2004/REC-xml-20040204/#AVNormalize.
From: Tim Howson [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 13, 2004 12:16 PMTo:
'[EMAIL PROTECTED]'Su
It's not ivory-tower theory, it's sheer pragmatism. Once you start
trying to repair broken documents, you enter a world where everything is
gray (not happy and shiny, believe me), and there's no guarantee that
one XML processor will behave the same as another. It's unlikely that
any two will impl
is the fix.
> -Original Message-
> From: David Kramer [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, September 21, 2004 11:10 AM
> To: [EMAIL PROTECTED]
> Subject: RE: Issue XERCESC-1235 (errors compiling with GCC)
>
> On Tue, 21 Sep 2004, Jesse Pelton wrote:
>
> > Th
The fix went in after 2.5. You'll have to pull from CVS or wait for 2.6
to get the fix. 2.6 is in the works, but I don't know when it will be
released. (It's worth noting that you can often get a more stable
system by pulling select bits from CVS. Xerces-C doesn't often do
bug-fix releases.)
X
And note the second "C" in "XERCESCROOT".
> -Original Message-
> From: David Cargill [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, September 15, 2004 9:22 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Build fails on Linux
>
>
>
>
>
> Hi Alex,
> What did you set your XERCESCROOT to? It s
Xerces does not include any way to create an instance document from a
DTD. I think projects to do that exist, however; you might find references in
the mailing list archive.
Note that your non-disclosure "Disclaimer" effectively prohibits you from
posting to public lists (like this one) tha
createDOMInputSource ();"
> > > throws an exception.
> > > Any idea?
> > >
> > > Regards,
> > > Michael Heeg
> > >
> > >
> > > try {
> > > XMLCh temp[100];
> > > XMLString::transcode("LS", te
keep me
from trying.
> -Original Message-
> From: Gareth Reakes [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, September 01, 2004 11:25 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Question concerning DOMBuilder and encoding
>
> Hi Jesse,
>
> Jesse Pelton wrote:
(m_xmlPath.data());
>
> DOMInputSource* myDOMSource = impl->createDOMInputSource ();
>
> myDOMSource->setEncoding(XMLString::transcode("iso-8859-1"));
> m_domDoc = m_domBuilder->parse(*myDOMSource);
> }
>
> > -Ursprüngliche Nachricht
Looking at the documentation, it appears that DOMBuilder::parse(const DOMInputSource
&source) should allow you to do what you want. You'll need to construct the input
source first, of course. As part of that process, you can call
DOMInputSource::setEncoding().
> -Original Message-
> F
g a new element with the
“<”). Any ideas?
-----Original
Message-From: Jesse
Pelton [mailto:[EMAIL PROTECTED] Sent: Monday, August 30, 2004 2:50
PMTo:
[EMAIL PROTECTED]Subject: RE: Less-than reserved character
sanity check...
If you
append a text node (or set an attribute,
e XML file (and it won’t validate) with
that “<” in the character data.
-Original
Message-From: Jesse
Pelton [mailto:[EMAIL PROTECTED] Sent: Monday, August 30, 2004 2:32
PMTo:
[EMAIL PROTECTED]Subject: RE: Less-than reserved character
sanity check...
Assum
Assuming you're letting Xerces do the serialization (by
using DOMWriter, for instance), just include '<' in your character data.
Xerces translates characters into the corresponding character entities as
needed.
From: Styduhar, Chris
[mailto:[EMAIL PROTECTED] Sent: Monday, August 3
; value. but
> that's one value at a time.
>
>
>
> but my struct is temp.one = value;
>
> temp.two = should be the next value;
>
> b/c it's looping thru value by value correct.
>
>
>
> -Original Message-
> From: Jesse Pe
}
> else
> {
>//here I have the data that I want to store,
> but I am inside the loop
>//so I thought I needed all the information
> first b/f storing into
>// my struct.
>//wri
does as well so I but I know the order of data won't change.
>
> -Original Message-
> From: Jesse Pelton [mailto:[EMAIL PROTECTED]
> Sent: Friday, August 13, 2004 2:29 PM
> To: [EMAIL PROTECTED]
> Subject: RE: storing data from XML file into data structure
>
&
If you can perform those two transformations (XML -> temp file and temp
file -> structure), what prevents you from performing a single
transformation (XML -> structure)? Presumably you've solved the problem
of avoiding overwrites in the course of implementing serialization to
and from your temp fi
Assuming that by "XML statements" you mean "XML documents" as defined in
the XML specification
(http://www.w3.org/TR/2004/REC-xml-20040204/#sec-well-formed), the spec
should provide the documentation you need. A well-formed XML document
consists of a prolog (principally the XML declaration), a roo
Doh. I stopped reading just before I got there. The schema for Schema
says the same thing, of course.
Can you reproduce this with DOMPrint -v=always -n -s -f using the Xerces
2.5? Having failed to come up with an explanation for why this wouldn't
work, I decided to try it. (Better late than ne
Well, I'm not sure I understand the spec fully on this point, but I
think you need to specify a value for the whiteSpace facet
(whiteSpace="collapse") in your schema. whiteSpace is among token's
constraining facets, but I don't see any indication that its default
value is collapse. The Schema spe
If you release a DOM document, all the memory it has
allocated for elements and so on is also released. If this were not true, your
process size growth would not be limited by the size of the largest document;
instead, the process would grow continuously. However, whether this memory will
be
Depends on what you mean by binary data. The XML spec
constrains what characters are allowed in documents. Typically an encoding like
base64 is used to represent binary data. base64Binary is even one of the simple
data types specified by XML Schema, which Xerces
supports.
From: Ashish Jain
If you specify a grammar that allows the parser to determine whether
whitespace in element content should be preserved, tell the parser to
validate, and setIncludeIgnorableWhitespace(false), you can ensure that
ignorable whitespace is not included in your DOM.
There are caveats, however. See
http
I found that I did not like the fact that DOMWriter puts out blank lines
in certain contexts, so I modified DOMWriterImpl.cpp to put an end to
that. I basically searched for any occurrences of printNewLine() that
was within a few lines of another occurrence and removed one of them. I
"fixed" 5 in
Try:
if
(theSerializer->canSetFeature(XMLUni::fgDOMXMLDeclaration,
false))
theSerializer->setFeature(XMLUni::fgDOMXMLDeclaration, false);
From: Mark Van Orman [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 15, 2004 7:05 PMTo:
[EMAIL PROTECTED]Subject: xml
de
If you didn't subscribe to the list, you missed the responses to your
first posting. You can find them in the mailing list archives.
-Original Message-
From: Joshua Bronson [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 14, 2004 2:25 PM
To: [EMAIL PROTECTED]
Subject: problems with WFXM
:01, Jesse Pelton wrote:
> That doesn't look like the current code. What version of Xerces are
> you using? What platform and compiler?
>
> -Original Message-
> From: Joshua Theman [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, July 14, 2004 1:56 PM
> To: [
That doesn't look like the current code. What version of Xerces are you
using? What platform and compiler?
-Original Message-
From: Joshua Theman [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 14, 2004 1:56 PM
To: [EMAIL PROTECTED]
Subject: problem with WFXMLScanner
I hope this list
Check out the DOMCount sample. It counts the elements in a document.
It sounds like you might want to count the unique element names, in
which case you'd need to adapt the code to your purposes.
-Original Message-
From: Daniele Carlucci [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 08,
When I upgraded to 2.0 (from 1.2a), I got a substantial performance
boost, thanks to the replacement of the DOM implementation (with 1.7's
IDOM). If you're already using IDOM, I doubt you'll see much, if any,
gain. If my recent experience upgrading to 2.5 is any indication, you
probably won't see
I've just upgraded an application that used Xerces 2.0 to 2.5. Our SAX
parser derives its own exception class from XMLException. The default
XMLException constructor sets the memory manager to NULL, and the
XMLException destructor assumes it's not NULL and blindly calls
fMemoryManager->deallocate
Depends on which URL you use. The first one in the original message had
"ww." instead of "www."
-Original Message-
From: Styduhar, Chris [mailto:[EMAIL PROTECTED]
Sent: Monday, June 28, 2004 1:22 PM
To: [EMAIL PROTECTED]
Subject: RE: Quick problem validating against schema located on a
Ch *namespaceURI,
const XMLCh *qualifiedName)
and the namespaceURI argument's value should be the same value as the
namespace attribute's value, "urn:ISBN:0-395-36341-6" or whatever, not "http://www.w3.org/2000/xmlns/".
Thanks to both of you for your help and sugge
Note that Adam's approach works by avoiding Xerces'
namespace processing. He appears to be mixing DOM 1 non-namespace aware calls
with DOM 2 namespace-aware calls, which is documented as potentially dangerous.
You may get away with it if you know enough about Xerces internals (and
they don't
I assume you want to append in your example. If this is the
case, you need to append it to the element. Element nodes can
have children; text nodes cannot.
-Original Message-
From: Fribault, Arnaud [mailto:[EMAIL PROTECTED]
Sent: Friday, June 18, 2004 11:29 AM
To: [EMAIL PROTECTED]
S
Actually, Attributes.hpp should be included via XMLReaderFactory.hpp. Alby's on to
the problem, though: the Attributes type is not known. I suspect this is a namespace
issue. Try XERCES_CPP_NAMESPACE::Attributes (or uncommenting "using namespace
XERCES_CPP_NAMESPACE;", since your code is buil
Have you looked at the SAXPrint sample app?
> -Original Message-
> From: Andre Stock [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, June 09, 2004 6:05 AM
> To: [EMAIL PROTECTED]
> Subject: Simple SAX-C++-Parser Documentation - Newbie
>
> Hi!
> I`ve various problems implementing a simple
Your message was received, but you might want to
consider whether your message footer is consistent with postings to a public,
and publicly archived, mailing list.
From: Steve Ichniowski
[mailto:[EMAIL PROTECTED] Sent: Monday, June 07, 2004
9:35 AMTo: [EMAIL PROTECTED]Subject:
Consider implementing your own FormatTarget. LocalFileFormatTarget is
very simple. Just clone it except for the constructors. You'll want
your own contructor that takes a FILE *, or perhaps a FileHandle. If a
Xerces FileHandle is a FILE * on your platform, all the constructor
needs to do is ass
will parse the document ?
>
> Thanks
>
> Pete
>
> -Original Message-
> From: Jesse Pelton [mailto:[EMAIL PROTECTED]
> Sent: 11 May 2004 14:08
> To: [EMAIL PROTECTED]
> Subject: RE: UTF-8 Encoding problem
>
>
> The text looks like straight ASCII in the mess
The text looks like straight ASCII in the message, which leads me to
wonder if it's been transmitted faithfully. Try sending it as an
attachment.
> -Original Message-
> From: Peter Guyatt [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, May 11, 2004 8:28 AM
> To: [EMAIL PROTECTED]
> Subject:
Title: Performance degradation
Hmm. I wonder if the pluggable memory manager introduced in
2.3 is responsible for the degradation. If I understand your benchmarks
correctly, changing from Xerces 2.2 or earlier to 2.3 or later results in a 28%
decrease in message throughput, from 50/sec to 36/
r this, but couldn't find the info that I needed.
> I'm just trying to ensure that I don't end up with
> memory leaks in my application.)
>
> Thanks,
> Monica
>
>
>
> --- Jesse Pelton <[EMAIL PROTECTED]> wrote:
> > From the Xerces API docu
>From the Xerces API documentation:
XMLCh* XMLString::transcode ( const char *const toTranscode ) [static]
Transcodes a string to native code-page.
NOTE: The returned buffer is dynamically allocated and is the
responsibility of
the caller to delete it when not longer needed. You can call
If you only need to create simple, highly stereotyped documents, you
might get up to speed more quickly by just generating text. A DOM
implementation makes it much easier to read, write, and use more varied
and/or complex documents, as well as ensuring that character encodings,
namespaces, and the
I don't remember how 1.6 dealt with filenames, but you could try putting
it into URL form: file:///c:/text.xml.
> -Original Message-
> From: Brian [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, April 06, 2004 10:08 AM
> To: [EMAIL PROTECTED]
> Subject: immediate exception on call to parse()
I take it back. Given the nature of his problem, that was a dumb thing to
say. But I stand by my suggestions (debugging, Purify-ing, building sample
apps).
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Friday, March 19, 2004 12:18 PM
> To: [EMAIL PROTE
I think that's a safe assumption. You're not spinning up any threads, and
Xerces surely isn't.
> -Original Message-
> From: Nathan Smith [mailto:[EMAIL PROTECTED]
> Sent: Friday, March 19, 2004 10:05 AM
> To: '[EMAIL PROTECTED]'
> Subject: RE: memory corruption when deleting the SAXParse
RE:
memory corruption when deleting the SAXParser
I
tried creating the parser object on the stack instead of the heap, and it
gave me access violations when setting the document handler. Will this
way work?
-Original Message-From: Jesse Pelton
ild All" selection in the
Biuld menu.
Then in the output pane it has
this:
memory
check error at 0x013FBDE0 = 0xE8, should be 0xFD.memory check error at
0x013FBDE1 = 0xBE, should be 0xFD.
-----Original Message-From: Jesse Pelton
[mailto:[EMAIL PROTECTED] Se
Title: Message
I
think that's the one. I'm having a hard time imaging why you can't release
memory that you just allocated if your settings are correct. Have you rebuilt
the project from scratch since making sure the settings are correct? If that
doesn't help, what is the exact text of the e
Title: Message
Have
you read the FAQ about mixing MS runtimes? It may be
relevant.
-Original Message-From: Nathan Smith
[mailto:[EMAIL PROTECTED] Sent: Thursday, March 18, 2004 2:14
PMTo: '[EMAIL PROTECTED]'Subject: RE: memory
corruption when deleting the SAXParser
Goo
Title: Message
There
is indeed a resource that may have the answer. I searched the mailing list
archive (http://marc.theaimsgroup.com/?l=xerces-c-dev)
for "unixware" and found a reference to bug 26953 (http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26953).
The bug has a patch that looks
This has nothing to do with your current problem, but will save you trouble
later: note that transcode() allocates memory, which you must release when
you're done with it.
> -Original Message-
> From: David --- [mailto:[EMAIL PROTECTED]
> Sent: Monday, March 15, 2004 7:00 AM
> To: [EMAIL
You're not releasing the sql_statements DOMNodeList.
> -Original Message-
> From: Patrick Wicki [mailto:[EMAIL PROTECTED]
> Sent: Friday, March 05, 2004 10:42 AM
> To: [EMAIL PROTECTED]
> Subject: Memory Trouble in DOMNode::getTextContent
>
>
> Hello,
> I still have memory trouble using
Based on
http://www.w3.org/TR/2000/REC-DOM-Level-2-Core-20001113/core.html#ID-1950641
247, I think you've got it right. However, if you want to use the node name
and value directly, you'll first need to check the node type as Hiran
suggested, just as you would before statically casting it. If your
A processing instruction doesn't have any structure (such as attributes and
other children); its contents are basically just text to be interpreted by
the XML processor (hence the name). You can get the target (in this case,
the string "udm") with getTarget(), and the remainder of the text in the P
emaining nodes
memory_size = get_node_memory_size(node_x);
if memory_size < max_memory_size
disk_size =
max_disk_size;
else
max_disk_size =
get_node_disk_size(node_x);
...
loop
Now,
how do I implement get_node_memory_size?
Thank y
Attribute ordering is insignificant in XML. If you rely on attribute
ordering, you're not using XML as specified (see, for instance,
http://mail.zope.org/pipermail/zope-dev/2002-May/016341.html). In other
words, you cannot count on a spec-compliant library like Xerces to support
this behavior. Ev
Title: Message
Presumably the limit is on the size of the serialized document. I doubt
there's a reliable way to determine that without performing the serialization.
Among the vagaries that you'd have to deal with if you were to track the size of
the document as you add to it are character en
1 - 100 of 299 matches
Mail list logo
