[jira] Closed: (XERCESC-1227) DOMDocument->getDocumentElement() returns NULL without any exception

2004-06-15 Thread jira
Message: The following issue has been closed. - View the issue: http://issues.apache.org/jira/browse/XERCESC-1227 Here is an overview of the issue: -

XSD import problem in xerces

2004-06-15 Thread Kiran BV
I validated a certain XSD in XMLSpy which xerces says it is invalid. I am not sure what the schema specs have to say about this. The scenario. A.xsd(targetNamespace="X") 1. includes B.xsd(targetNamespace="X") that imports targetNamespace="Y" using M1.xsd 2. includes C.xsd(ta

RE: Newbie Problems with Simple SAXParser

2004-06-15 Thread Andre Stock
It was actually the namespace missing in the signature of startElement().I thought if Attributes.hpp is included and the namespace was declared in my application it should work! OK, now i know better! Thank you very much indeed! Andre > Actually, Attributes.hpp should be included via XMLReade

RE: Newbie Problems with Simple SAXParser

2004-06-15 Thread Jesse Pelton
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

RE: Newbie Problems with Simple SAXParser

2004-06-15 Thread Tony Dodd
You need to include the header file that defines Attributes, directly or indirectly. Tony Dodd Oxford University Research Technology Group >-Original Message- >From: Andre Stock [mailto:[EMAIL PROTECTED] >Sent: 15 June 2004 15:18 >To: [EMAIL PROTECTED] >Subject: Re: Newbie Problems with

Re: Newbie Problems with Simple SAXParser

2004-06-15 Thread Andre Stock
Hi, I just took the startElement method from SAX2Count and copied it to my .hpp (the definition) and my .cpp file (declaration). I did the same for the characters method from SAX2Count. When i compile my project, the compiler says that there is a ',' missing before '&'(in my .hpp and my .cpp file!)

RE: operator new

2004-06-15 Thread Robert Buck
I'm actually asking if you forgot the inline keyword in your own code for the "nafxcwd.lib" library. It has been my experience that when I see this sort of error, usually there's a missing inline keyword somewhere. --Bob -Original Message- From: Milan Tomic [mailto:[EMAIL PROTECTED] Sent

RE: operator new

2004-06-15 Thread Milan Tomic
Title: Message Hello Bob,       Could you, please, tell me more about it? Is it some known Xerces issue? How can I find its ID in bugzilla?   Thank you, Milan     -Original Message-From: Robert Buck [mailto:[EMAIL PROTECTED] Sent: Thursday, June 10, 2004 2:22 PMTo: [EMAIL

Re: Newbie Problems with Simple SAXParser

2004-06-15 Thread Alberto Massari
Hi Andre, you are missing a #include in the CHandler.hpp file. Alberto At 13.43 15/06/2004 +0200, Andre Stock wrote: Ok, you`re right i`m new to c++. But anyway i want to try to write it on my own (or better with your help! ;-)) That`s the CXercesTest.cpp file: #include "stdafx.h" #include "CXerce

[jira] Created: (XERCESC-1229) Runtime error R6025 pure virtual function call

2004-06-15 Thread jira
Message: A new issue has been created in JIRA. - View the issue: http://issues.apache.org/jira/browse/XERCESC-1229 Here is an overview of the issue: -

Re: Assertion error when executing SAXparser

2004-06-15 Thread Alberto Massari
At 11.58 15/06/2004 +0200, Andre Stock wrote: Thanks for the explanation, i hopefully got it! So when the parser detects a new element the startElement method (or its overwritten version)is called and is given the parameters (uri,localname,qname and attributes) which i can use in my application, ri

Re: Assertion error when executing SAXparser

2004-06-15 Thread Andre Stock
Thanks for the explanation, i hopefully got it! So when the parser detects a new element the startElement method (or its overwritten version)is called and is given the parameters (uri,localname,qname and attributes) which i can use in my application, right? Do i have to include another header file