I'm using Apache Xerces-C V1.4.0.
I've got two DOM_Documents in memory, and I want to subtitute a DOM_Node
instance
from one DOM_Document for a DOM_Node instance in another DOM_Document
Doc1:
-
...oldChildern.. //
oldChild
Hi,
The Xerces DOM parser seems to be crashing in a multithreaded
env.
I tried running the thread test program (attached to this
mail). This is the thread
test program that [EMAIL PROTECTED] had posted
with a similar problem earlier.
He uses Xerces 1.4, I use Xerces 1.2.0.
Heres the results I got
Apparently whatever that was got fixed in CVS since yesterday :) (and not in
Xalan, in Xerces, as I purposely have Xalan sticky tagged to some date in
March when I know this was working and started sliding Xerces around). If
you are curious, the issue had something to do with the xmlns prefix not
The previous ostream os; mistake that Anand made aside, these new issues
shouldn't be ignored as they _are_ being caused by DOMPrint.cpp.
The problem here is that DOMPrint.cpp wasn't written with usability in mind.
Don't let the fact that it LOOKS like an insertion operator confuse you. If
you l
Well, with the upcoming 1.5 release, I think that
the XML parser has now pretty much moved beyond me. And Tinny and crew, and
associated third party others, have it under control pretty well at this point I
think.
I have a big personal project coming up soon that
will be taking up all my t
Well, with the upcoming 1.5 release, I think that
the XML parser has now pretty much moved beyond me. And Tinny and crew, and
associated third party others, have it under control pretty well at this point I
think.
I have a big personal project coming up soon that
will be taking up all my t
Well, with the upcoming 1.5 release, I think that
the XML parser has now pretty much moved beyond me. And Tinny and crew, and
associated third party others, have it under control pretty well at this point I
think.
I have a big personal project coming up soon that
will be taking up all my t
One second, I know where the bug is . I will fix it in the nightly build.
Tinny
Tinny Ng wrote:
> David,
>
> > SAXParser in the 1.5 release now defaults to doing namespace processing.
> No, I didn't make this. The default namespace setting for SAXParser still
> "supposed" to be off, unle
David,
> SAXParser in the 1.5 release now defaults to doing namespace processing.
No, I didn't make this. The default namespace setting for SAXParser still
"supposed" to be off, unless there is a bug. In XMLScanner constructor, the
fDoNamespace is false. And it is set to true if setDoNamespac
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2238
*** shadow/2238 Tue Jun 19 11:58:28 2001
--- shadow/2238.tmp.25106 Tue Jun 19 11:58:28 2001
***
*** 0
--- 1,52
+ ++
+ | libWWW problems wi
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2237
*** shadow/2237 Tue Jun 19 11:42:46 2001
--- shadow/2237.tmp.25054 Tue Jun 19 11:42:46 2001
***
*** 0
--- 1,53
+ ++
+ | libWWW redirect er
SAXParser in the 1.5 release now defaults to doing namespace processing. I
think it must be related to some change in the default behavior of
XMLScanner, but I haven't had a chance to investigate.
This seems wrong as there is no way to get namespace information through
the SAX1 DocumentHandler.
Peter,
To avoid your bug report get lost in the mailing list, please open a Bugzilla
Bug for the problem you found. See
http://xml.apache.org/xerces-c/bug-report.html for detail.
For other bugs you reported earlier (e.g. internalSubset related), I will try to
keep track of them. But to be safe
Hi Jeetu,
Where can I get some more information on the memory management issue
in Xerces.
Have you posted it somewhere ??
Thanks for your reply to my query.
Nikita
[EMAIL PROTECTED] wrote:
When
one calls the getDocument() on a parser instance, one is getting back a
reference to the DOM_Document
Thanks folks. As for the MemParse example, the first line had scrolled off
the screen and I was missing out on seeing the error message that is the
first line of the output of the MemParse code.
> -Original Message-
> From: Erik Schroeder [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, June 1
Jeetu,
XML error is not thrown through XMLException, it is issued through Error
Handler. So in sample Memparse, after you set the MemParseHandler as the
error handler:
MemParseHandlers handler;
parser.setErrorHandler(&handler);
The XML error will be issued through MemParseHandlers::fat
"Khaled Noaman" <[EMAIL PROTECTED]> writes:
> The DecimalDatatypeValidator fix is in CVS. Would you please extract
> the latest version of the file and try again?
Works fine now, thanks.
jas.
-
To unsubscribe, e-mail: [EMAIL P
Install an error handler, much like you installed a document handler.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, June 19, 2001 12:27 PM
To: [EMAIL PROTECTED]
Subject: RE: DOMParser does not report errors for XML that are not well-fo
rmed
Peter,
It does not throw an exception, it calls the error handler.
--
Dean Roddey
Software Geek Extraordinaire
Portal, Inc
[EMAIL PROTECTED]
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, June 19, 2001 10:27 AM
To: [EMAIL PROTECTED]
Subject: R
- Original Message -
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, June 19, 2001 8:27 PM
Subject: RE: DOMParser does not report errors for XML that are not
well-formed
> Peter,
> You could also try this out with the MemParse sample code that comes along
> with the pack
Peter,
You could also try this out with the MemParse sample code that comes along
with the package. If you modify the
string in gXMLInMemBuf variable in MemParse.cpp from a well-formed XML
string to a not well-formed one and try running the sample code, you will
see the behavior that I am seeing.
- Original Message -
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, June 19, 2001 7:31 PM
Subject: DOMParser does not report errors for XML that are not well-formed
> I am using a DOMParser instance to load XML from a string or a file to a
DOM
> by calling the parse(Inp
When one calls
the getDocument() on a parser instance, one is getting back a reference to the
DOM_Document member of the parser. And since Xerces has a reference counting
mechanism, your document reference should be fine even if your parser instance
goes out of scope. (people, correct me if
Seems that ENTITY_NODE is not printed correctly (DOMPrint.cpp sample)
Below is the snapshot. It just writes the plain information about this node,
like
Here the rules from XMLrec:
EntityDef::=EntityValue | (ExternalID NDataDecl?)
ExternalID::='SYSTEM' S SystemLiteral | 'PUBLI
You need to set dependencies in Visual C++ so that your application is
linked using the necessary libraries. See the Visual C++ documentation for
more information on how to set dependencies.
Hint: select "Dependencies" from the "Project" menu.
Dave
I am using a DOMParser instance to load XML from a string or a file to a DOM
by calling the parse(InputSource...) method on the string. When the XML
string is not well-formed, I do not get any exceptions (I am catching
XMLException while parsing).
So I looked at the MemParse sample code which us
DOMCount or DOMPrint are good samples showing how to create
instances of DOMParser, setting the parser and parse an instance
document.
To simplify the creation of your own application, you may use
the sample DOMCount and add in your own stuff if you don't mind
reusing the name.
Regards,
I have installed XERCES-C successfully and the examples are running fine.
I want to write my own examples.How should I begin?
I am reading the programming guide and it says that we have to create
instances of XMLParsers and XMLReaders.
Where should I create those instances.
Where do we have to st
Upon the base of one of the samples given (XalanTransform) i am trying to
make a DLL. But i have linker errors as you can see at the bottom of this
mail.
I have set up a project called 'Test' in the workspace 'Samples'. Here is
the code of the test.cpp. Thank you to help me.
--
Martin,
Thanks for the response.
I was able to build the libary linking with libCsup_v2.2. My options
were not exactly as the ones you mentioned here. I will also try with
these options.
Regards,
Fereshteh
>
> - Original Message -
> From: "Karimeddini, Fereshteh" <[EMAIL PROTECTED]>
>
Java and C++ are case-sensitive languages. Change GetChildNodes() to
getChildNodes()
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Here the piece of code from dom/NodeImpl.hpp
// define 'null' is used extensively in the DOM implementation code,
// as a consequence of its Java origins.
// MSVC 5.0 compiler has problems with overloaded function resolution
// when using the const int definition.
//
#if defined(XML_CSET)
cons
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: RE: 'GetChildNodes' is not a
Hi,
Try a lower-case g...
New_Sons = Node_Son.getChildNodes();
"XML MAN"
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
Hi again!
I am trying to build a function, whose parameter is 'List'
(DOM_NodeList):
---//
DOM_Node Node_Son;
DOM_NodeList New_Sons;
long Number_Sons;
int i;
Number_Sons = List.getLength();
for (i = 0; i < Number_Sons; i++) {
Node_Son = List.item(i);
if (Node_Son.getNodeType()
36 matches
Mail list logo
