+1
On Mar 31, 2004, at 1:44 AM, Neil Graham wrote:
Hi all,
Throughout January and February, the idea [1] of converting the XML
project
into a "Federation" of projects was discussed. The reason for doing
this
is that the by-laws of the Apache Software Foundation make certain
assumptions
Gareth,
You could add a link to http://www.xs4all.nl/~ewh/DOMSerializer/ or put the
files there on your site. It's a utility to serialize DOM_Nodes to a stream.
Useful until the level 3 serializing stuff gets released, I suppose.
Evert
> -Original Message-
> From: Gareth Reakes [mailto:
Works a treat for me
> -Original Message-
> From: Markku Pirila [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, June 06, 2002 12:32 PM
> To: [EMAIL PROTECTED]
> Subject: Borland C++ Builder 5 Professional
>
>
> Hi,
>
> I would like hear experiences about using compiler mentioned in subjec
David,
You can try using the attached code to prettify the DOM.
Hope this helps,
Evert
> -Original Message-
> From: David R. [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, May 23, 2002 3:37 PM
> To: [EMAIL PROTECTED]
> Subject: Pretty printing a DOM tree
>
>
>
> I am using a piece of cod
Hi,
That's not currently part of the DOM spec (will be in level 3) and not part
of xerces.
Standard answer: modify the DOMPrint example. But I've already done that, so
you can use that code. Take a look at
http://www.xs4all.nl/~ewh/DOMSerializer
Share & enjoy,
Evert
-Original Message-
You can download the sources for the serializer Jesse refers to from
http://www.xs4all.nl/~ewh/DOMSerializer/
There's some documentation there, as well.
T, Evert
> -Original Message-
> From: Jesse Pelton [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, May 14, 2002 7:42 PM
> To: '[EMAIL PROTE
Ideshini,
I've written a utility class to do just that (based on the DOMPrint
example) - you can find the code and some documentation at:
http://www.xs4all.nl/~ewh/DOMSerializer
Share & enjoy
Evert
-Original Message-
From: Ideshini Naidoo [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April
I don't think that'll work, as xerces uses exceptions internally when
parsing, for instance to detect end-of-entity and such.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Thursday, April 04, 2002 9:59 AM
To: [EMAIL PROTECTED]
Subject: using xerces C with exc
Yuri,
There is no provision for that: it'll be introduced in DOM level 3. The
standard answer is to 'look at teh DOMPrint sample and amend it to your
needs' I've done just that and you can have the result: a class called
DOMSerializer that allows you to stream an in-memory DOM tree to file. See
a
Leo,
Indeed, the serializer does not format the document. I have a small utility
that does that separately, which I attach - it inserts whitespace as needed.
It's very straightforward, but it may serve your purpose.
Share & enjoy
Ta, evert
-Original Message-
From: Leonardo B. Lopes [
I think you could use your own XMLValidator derived class when constructing
the parser. See the docs for the constructor of the parser and for
XMLValidator.
HTH, Evert
-Original Message-
From: Arun Ramdas [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, February 13, 2002 8:24 PM
To: [EMAIL PR
Smita,
I've written a small class that can stream a DOMTree to a std::ostream. If
you use that with a std::stringstream you're in business.
HTH, Evert
> -Original Message-
> From: Smita [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, February 05, 2002 21:49 PM
> To: [EMAIL PROTECTED]
> Subj
Don,
I never quite solved it, but at the time, I got this email:
>This behavior is probably caused by a C++ Builder bug in compilation
>of the Unicode resource files. After replacing the 'hex dump'-messages,
>by extracting them from precompiled binary, to 'string'-format, the
>Win32MsgLoader::lo
Don,
Does the current version of the BCB stuff generate good exceptions when
parsing? There used to be a problem with the resource compiler which meant
that WinMsgLoader always yields an empty message.
TIA, Evert
> -Original Message-
> From: Don Mastrovito [mailto:[EMAIL PROTECTED]]
> S
>
> I remember the origin of the problem, and why the external subset
> was not written in the XML by the supplier of the message :
> because we then had problems with the real localisation of the
> file, in the machine where the app using Xerces runs.
> For example, the line for the DTD which was
Laurent,
You can set up an empty document that does have the DOCTYPE, create a parser
for that and reuse that parser for new documents.
Here's an example of what that would look like that Alberto Massari sent me
ages ago:
XMLByte* dummyXML=" ";
MemBufInputSource inputSource(dummyXML,strlen(dum
I think you want to use DOM_Document::getElementsByTagName. See the manual
entry for that.
> -Original Message-
> From: Ravi_Jain [mailto:[EMAIL PROTECTED]]
> Sent: Monday, December 03, 2001 10:19 AM
> To: [EMAIL PROTECTED]
> Subject: RE: Hi ...Help required for DOM Parser
> Sensitivity:
Neil,
Check out Project|Options|DLLs to delay load
That's what you want, I think.
Evert
> -Original Message-
> From: Neil Sherman [mailto:[EMAIL PROTECTED]]
> Sent: Friday, November 30, 2001 10:26 AM
> To: '[EMAIL PROTECTED]'
> Subject: Dynamically linking xerces while the program is r
It's fairly straightforward, really: you can just use any ostream and stream
a DOM_Node into it. For example,
DOM_Node node;
cout << node;
should work. In this manner, the DOM_Node and its children are written using
UTF-8. If you want to use another decoding, you must create your own
serializer.
Liamliu,
The thing is that localname is a XMLCh*, not a char*. You can use transcode
to convert between the two.
hth, evert
> -Original Message-
> From: liu lang [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, November 15, 2001 10:22 AM
> To: [EMAIL PROTECTED]
> Subject: A small question a
Try this...
> -Original Message-
> From: Paul Tan [mailto:[EMAIL PROTECTED]]
> Sent: Monday, October 01, 2001 5:24 AM
> To: [EMAIL PROTECTED]
> Subject: Serialize DOM_Node
>
>
> Hi,
>
> is there any way to serialise a DOM_Node (extract from the DOM
> Tree) into a
> string (or XMLCh) ?
Ana,
I've written a class that outputs XML to any stream. Feel free to use and
amend it. No warranties :)
> -Original Message-
> From: Ana Raquel Gouveia Amaro [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, September 20, 2001 18:06 PM
> To: xerces C++ XML
> Subject: generating XML through
The whitespace in the document is read and stored by the parser. The
DOMWriter simply writes everything (including whitespace) in the document.
To strip ignorable whitespace, set the parser's flag to exclude it with
DOMParser::setIncludeIgnorableWhitespace(false);
Ta, evert
> -Original Messa
DOM_Element elt = (DOM_Element&) node;
> -Original Message-
> From: Vinodkumar S [mailto:[EMAIL PROTECTED]]
> Sent: Monday, July 30, 2001 10:14 AM
> To: '[EMAIL PROTECTED]'
> Subject: Doubt
>
>
> How can Convert a DOM_Node of nodetype Element to DOM_Element,
>
> rgrds
> Vinod
>
> ---
Well, maybe I can help you out with this serializer I wrote (it's been
posted here before). Hope it works for you. No guarantees, though.
Ta, evert
> -Original Message-
> From: Dodson, John [mailto:[EMAIL PROTECTED]]
> Sent: Saturday, July 28, 2001 2:30 AM
> To: '[EMAIL PROTECTED]'
> Sub
Ehmm, Jeremy, you're creating a new XmlErrorReporter() in every iteration;
maybe you should try deleting that?
> -Original Message-
> From: Jeremy Ford [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, July 18, 2001 16:58 PM
> To: [EMAIL PROTECTED]
> Subject: memory usage/performance for xer
Hi all,
I've got an application where I use XML documents that _must_ adhere to a
certain, known, DTD.
What I'd like to be able to do is force my DOMParser (or its Validator, or
whatever) to always use a DTDValidator with that DTD to validate documents,
even if their DOCTYPE is missing or says th
Can be done (at least, I do it), e.g.
std::map
> -Original Message-
> From: Erez Greenstein [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, July 10, 2001 10:30 AM
> To: '[EMAIL PROTECTED]'
> Subject: using XML DOM with STL
>
>
>
> I am trying to use STL map with DOM_Node as its value ?
M
> To: [EMAIL PROTECTED]
> Subject: Re: inlining a DTD
>
>
> "Evert Haasdijk" <[EMAIL PROTECTED]> writes:
>
> > Is there any way to inline the DTD for a DOM document so that, after
> > writing the document, it has an inline DTD?
>
> My solution is to start
Hi all,
Is there any way to inline the DTD for a DOM document so that, after writing
the document, it has an inline DTD?
TIA, Evert
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
> -Original Message-
> From: Jason E. Stewart [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, July 05, 2001 20:49 PM
> To: [EMAIL PROTECTED]
> Subject: Re: creating element with ID in a document
>
>
> "Evert Haasdijk" <[EMAIL PROTECTED]> writes:
>
&
Francois,
Alas, the internal map of Ids is only updated during a parse. AFAIK, you
have two options:
1. write your document to a stream after creating the attribute, parsing
that and from then on working with the newly parsed doc (by no means ideal,
but apparently the only way to do this in DOM
Use DOM_Document::importNode() to transfer nodes from one document to
another.
You'd get something like:
// Find oldChild in doc1
DOM_Element oldCreationInformationElem =
mp7->findElementByName("CreationInformation", 0);
// Find newChild in doc2
D
Oops; replied without thinking; it's not a DOM_Element member at all - it
just starts with a lowercase 'g'
Sorry
> -Original Message-----
> From: Evert Haasdijk [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, June 19, 2001 12:54 PM
> To: [EMAIL PROTECTED]
> Subject
You have to cast it to a DOM_Element to do that:
New_Sons = ((DOM_Element&) Node_Son).GetChildNodes();
> -Original Message-
> From: XML MAN [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, June 19, 2001 11:51 AM
> To: [EMAIL PROTECTED]
> Subject: 'GetChildNodes' is not a me
Anand,
If you want to write to cout, just use
DOM_Node node = parser->getDocument();
cout << node;
ta, evert
> -Original Message-
> From: Awasthi, Anand [mailto:[EMAIL PROTECTED]]
> Sent: Monday, June 18, 2001 16:58 PM
> To: '[EMAIL PROTECTED]'
> Subject: problem in DOMPrint.cpp
>
>
> -Original Message-
> From: Joseph Garry (TT) [mailto:[EMAIL PROTECTED]]
> Sent: Friday, June 15, 2001 17:35 PM
> To: '[EMAIL PROTECTED]'
> Subject: DOM output to file
>
>
> I would assume that writing out a DOM tree to a file would be a
> straightforward operation. However, scanning
Anand,
Here's an example of a class I wrote to do just that.
Feel free to use this code; it writes to any std::ostream, so you can use it
for files, strings or stdout. No warranties, though ;-)
Share and enjoy!
> -Original Message-
> From: Awasthi, Anand [mailto:[EMAIL PROTECTED]]
> Se
I had the same problem, and I've solved it by having a skeleton XML
document in memory. I initialise the new document by parsing the skeleton
document in a MemBufInputSource and then append / insert any nodes I need in
that new document.
Here's sopme example code:
// In-memory template for empty
As Kiuma says, you can'y use the MSVC DLL with borland. You can either build
the xerces DLL with Borland. There's a BCB4 project (which you can use with
BCB5 without hassle) at:
http://xml.apache.org/websrc/cvsweb.cgi/xml-xerces/c/Projects/Win32/BCB4/
Regards, evert
> -Original Message-
>
> >DOM_Node* nodePtr = new DOM_Node(node); //
> calls copy
> contructor
>
> May work in some implementations. Won't work in others. May not work in
> future releases of this DOM, and if it stops working you have
> only yourself
> to blame.
>
> Node.cloneNode() is a portable
On the other hand, if you've created a DOM_Node as you describe, you may use
the following (at least, it works for me)
DOM_Node node; // created using the DOM API
DOM_Node* nodePtr = new DOM_Node(node); // calls copy contructor
// use nodePtr, pss
Benoit,
I think you should have a map rather than . (DOM_Element, like almost all DOM_XXX classes is a kind of
smart pointer).
But then, why have a map at all? The DOM API allows easy access to nodes and
all that - it's what it's for.
Ta, evert
> -Original Message-
> From: Benoit Lefev
+1
>
> Hi there,
>
> I would like to propose that Pei Yong Zhang be given CVS commit access
> for the Xerces-C project.
>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Pallavi,
There's no need to delete the DOM_Node yourself; as you suggest yourself,
xerces keeps a reference count and automagically frees memory.
ta, evert
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e
No, I never got any reaction to that message...the problem did go away of
it's own accord, though - scary.
Which email address did youy use?
> -Original Message-
> From: Dallas Harken III [mailto:[EMAIL PROTECTED]]
> Sent: Friday, May 25, 2001 1:15 AM
> To: [EMAIL PROTECTED]
> Subject: F
See http://marc.theaimsgroup.com/?l=xerces-c-dev
> -Original Message-
> From: Mark Cridge [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, May 16, 2001 13:15 PM
> To: [EMAIL PROTECTED]
> Subject: mail archives unavailable
>
>
> Are there any archive mirrors?
>
> Mark
>
>
> -
;
> --
> Dean Roddey
> Software Geek Extraordinaire
> Portal, Inc
> [EMAIL PROTECTED]
>
>
>
> -Original Message-
> From: Evert Haasdijk [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, May 10, 2001 5:18 AM
> To: [EMAIL PROTECTED]
> Subject: Win32Ms
Hi all,
I've compiled xerces-c with Borland C++ Builder 5 and all seems well.
However, Win32MsgLoader::loadMsg() always results in an empty string.
Has anybody else come across this problem? Any ideas about a fix?
I'm running W2K and BCB. The problem occurs with both the stable and the
nightly s
Hi all,
When modifying or creating a DOM_Document in memory, there seems to be only
one way to check that the results are valid in terms of the DTD. Also,
a lot of information is generated during the parse of a stream that cannot
be updated through the DOM (e.g. DOM_Document::getElementById() onl
There is no serialization in xerces-c, so everybody ends up modifying the
DOMPrint example.
Me, too, and you can have it.
No warranties, mileage may vary and so on.
Good luck, e
DOMSerializer.cpp
DOMSerializer.hpp
-
To unsubs
Hi all,
There doesn't seem to be any way to add an attribute to a DOM_Element and
specify that it's an ID. Similarly, changing the content of an ID atttribute
isn't - as far as I can tell - reflected in the document.
Is there any way around this? I know that you can tell an AttrImpl that it's
an
rting ID
//
//}
//else {
//// Kids carry value
//deep = true;
//}
}
break;
// SNIPPETYSNIP
> -Original Message-
> From: Evert Haasdijk [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, April 24, 2001 13:26 PM
> To: [E
Hi all,
My application 'copies' part of an XML document into another (using
DOM_Document::importNode()). Now, some of the imported DOM nodes have an ID,
but I can't retrieve them after importing them (calling
DOM_Document::getElementById()) because the document's fNodeIDMap isn't
updated on impor
Oops...I missed some of the casts I needed...see attached files
> -Original Message-
> From: Evert Haasdijk [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, April 18, 2001 9:57 AM
> To: [EMAIL PROTECTED]
> Subject: RE: Changes for C++Builder 4
>
>
> Hi William,
>
Hi William,
I didn't see your earlier posting, but anyway, here's my $0.02.
>1. Am I correct that Visual C++ 6 does not declare the C++ standard type
>"wchar_t" as intrinsic like C++Builder does, which allows VC6 to think an
>"XMLCh" is the same, while C++Builder thinks they are different?
It
Yakov,
I've modified the DOMPrint example to provide a class DOMSerializer.
Included are the source and header for that class for you (and anyone else)
to use.
Hope this helps you.
Ta, Evert
DOMSerializer.cpp
DOMSerializer.hpp
-
Hi all,
I've (like many, many others, no doubt) written a class to serialize a DOM,
based on the DOMPrint example. However, when I delete the
XMLFormatter I use, I get an access violation in
XMLFormatter::~XMLFormatter(), where it does 'delete fXCoder' (the last line
in the destructor).
Any ideas
58 matches
Mail list logo
