Re: Configuring on QNX

Hi Gareth, I'm not very experienced with QNX, so I'm not sure how much help I could be. >From what I can gather my problem is related to the way you currently generate the Makefiles, so this move to a new build system could help resolve that issue. If the move to a standard configure/make/make i

[jira] Commented: (XERCESC-1380) Unneccessary definition of extra delete operator causes compiler error

[ http://issues.apache.org/jira/browse/XERCESC-1380?page=comments#action_61027 ] David Bertoni commented on XERCESC-1380: > So anyway why do you need to define that extra delete operator? Because the C++ standard requires it, for the desired ru

[jira] Created: (XERCESC-1382) Unreliable bool definition for compilers without bool type

Unreliable bool definition for compilers without bool type -- Key: XERCESC-1382 URL: http://issues.apache.org/jira/browse/XERCESC-1382 Project: Xerces-C++ Type: Bug Versions: 2.6.0 Environment: Solaris

[jira] Created: (XERCESC-1384) Inconsistent definition and declaration of a method TraverseSchema::processSubstitutionGroup

Inconsistent definition and declaration of a method TraverseSchema::processSubstitutionGroup Key: XERCESC-1384 URL: http://issues.apache.org/jira/browse/XERCESC-1384 Project: Xerces

[jira] Created: (XERCESC-1383) Definition of table in GeneralAttributeCheck class with error

Definition of table in GeneralAttributeCheck class with error - Key: XERCESC-1383 URL: http://issues.apache.org/jira/browse/XERCESC-1383 Project: Xerces-C++ Type: Bug Versions: 2.6.0 Environment: So

[jira] Updated: (XERCESC-1381) Memory Leak in GrammarResolver class

[ http://issues.apache.org/jira/browse/XERCESC-1381?page=history ] Christian Will updated XERCESC-1381: Attachment: GrammarResolver.cpp.patch my changes... > Memory Leak in GrammarResolver class > > > Ke

[jira] Created: (XERCESC-1381) Memory Leak in GrammarResolver class

Memory Leak in GrammarResolver class Key: XERCESC-1381 URL: http://issues.apache.org/jira/browse/XERCESC-1381 Project: Xerces-C++ Type: Bug Components: Validating Parser (Schema) (Xerces 1.5 or up only) Versions: 2.6.0

[jira] Created: (XERCESC-1380) Unneccessary definition of extra delete operator causes compiler error

Unneccessary definition of extra delete operator causes compiler error -- Key: XERCESC-1380 URL: http://issues.apache.org/jira/browse/XERCESC-1380 Project: Xerces-C++ Type: Bug Versions: 2.6.0

[jira] Created: (XERCESC-1379) XSSimpleTypeDefinition constructor - declaration and definition of a variable at the "if" check causes compiler error

XSSimpleTypeDefinition constructor - declaration and definition of a variable at the "if" check causes compiler error - Key: XERCESC-1379 URL: http://issues.apache

Re: Relative paths in C++ on Macintosh OS X

Steve, getcwd() works for me. You might try printing out what it returns at the very start of your program. Is it possible that something else in your code is calling chdir or fchdir? -jdb On Mar 16, 2005, at 11:38 AM, Steve Smith wrote: Indeed, you are correct. getcwd is returning "/". This s

Re: Relative paths in C++ on Macintosh OS X

Indeed, you are correct. getcwd is returning "/". This seems strange, given that the C++ code is writing files relative to the build directory correctly. I am using paths relative to the exe location and those are working correctly. Why the difference? (and more importantly, what can I do about

Advanced novice question about PSVI

To All, I have a question whether I can use PSVI for an algorithm I have in mind... My goal is to take the content model from XSD schema documents and transform it into an ordered graph/tree that can be used to serialize application data in the order corresponding to the content model. If the sc

Re: Relative paths in C++ on Macintosh OS X

Steve, Could you do a bit of debugging on this? One way or another, the relative path should be resolved inside XMLParsePathToFSRef_X in MacOSPlatformUtils.cpp. This would be either in response to getCurrentDirectory (which calls XMLParsePathToFSSpec with the path "."), or with the entire relati

[jira] Commented: (XERCESC-1378) wrong string destruction in MemBufInputSource::~MemBufInputSource()

[ http://issues.apache.org/jira/browse/XERCESC-1378?page=comments#action_60986 ] Gareth Reakes commented on XERCESC-1378: Hey, Nikolay Ognyanov (JIRA) wrote: > [ > http://issues.apache.org/jira/browse/XERCESC-1378?page=comments#action_60

Re: [jira] Commented: (XERCESC-1378) wrong string destruction in MemBufInputSource::~MemBufInputSource()

Opps, sorry everyone, forgot to add it to the bug. Cheers, Gareth -- Gareth Reakes, Managing Director Parthenon Computing +44-1865-811184 http://www.parthcomp.com - To unsubscribe, e-mail: [EMAIL PROTECTED] Fo

Re: [jira] Commented: (XERCESC-1378) wrong string destruction in MemBufInputSource::~MemBufInputSource()

Hey, Nikolay Ognyanov (JIRA) wrote: [ http://issues.apache.org/jira/browse/XERCESC-1378?page=comments#action_60981 ] Nikolay Ognyanov commented on XERCESC-1378: --- I agree with the part about BinMemInputStream. I disagree however about the local

[jira] Commented: (XERCESC-1378) wrong string destruction in MemBufInputSource::~MemBufInputSource()

[ http://issues.apache.org/jira/browse/XERCESC-1378?page=comments#action_60981 ] Nikolay Ognyanov commented on XERCESC-1378: --- I agree with the part about BinMemInputStream. I disagree however about the local copy in MemBufInputSource. I see n

AW: Getting a parser from a string

Hi João, i hope the code below is a helping hand. i did it that way and it worked. "pToContent" is an LPCTSTR and contains the string i want to parse. Best regards Mirko static const XMLCh gLS[] = { xercesc::chLatin_L, xercesc::chLatin_S, xercesc::chNull }; xercesc::DOMImplementatio

RE: Relative paths in C++ on Macintosh OS X

I'm using xcode (1.5) with the default gcc 3.3 and OS (10.3.8) and the latest xerces (2.6 I believe, this behavior was the same for other recent releases). We're initializing the parser with: xercesc::XMLPlatformUtils::Initialize(); mParser.reset( new xercesc::XercesDOMParser() );

[jira] Commented: (XERCESC-1378) wrong string destruction in MemBufInputSource::~MemBufInputSource()

[ http://issues.apache.org/jira/browse/XERCESC-1378?page=comments#action_60978 ] Gareth Reakes commented on XERCESC-1378: Hi, My reading of the code is slightly different. BinMemInputStream does not delete if fAdopted is set, but rather if

Re: Overflow Vulnerability In SAX2Count Demo Program

Hey, Cheers, patch is in cvs. Gareth [EMAIL PROTECTED] wrote: Here is a patch to fix a buffer overflow in CVS revision 1.29 of samples/SAX2Count/SAX2Count.cpp. The code used strcpy() to place a user-supplied command line option into a 64-byte buffer localeStr. I've replaced this with a strn

Re: Relative paths in C++ on Macintosh OS X

Steve, I don't know of a problem in this area. I've used relative paths successfully. But your setup may be somewhat different. Can you provide more information about the context in which you're seeing this issue? Build environment? Compiler? What API you're passing the relative path to? Can y

[jira] Created: (XERCESC-1378) wrong string destruction in MemBufInputSource::~MemBufInputSource()

wrong string destruction in MemBufInputSource::~MemBufInputSource() --- Key: XERCESC-1378 URL: http://issues.apache.org/jira/browse/XERCESC-1378 Project: Xerces-C++ Type: Bug Components: SAX/SAX2

RE: Getting a parser from a string

João, I can't remember what the default encoding setting for MemBufInputSource is, but it may be that you need to set the encoding to single-byte characters. -Original Message- From: João Graça [mailto:[EMAIL PROTECTED] Sent: 16 March 2005 03:01 To: xerces-c-dev@xml.apache.org Subject: Ge

Antwort: Re: XML OO Parametrization

Hi Axel, thank you for the reply! Regarding the validation: Are there any transformations available, which turn the schema into a GUI / PHP page oder editors, which do validation on-the-fly? Regarding the construction of the object: Is it a good idea for the helper classes to have a constructor

Getting a parser from a string

Hello, I am trying to start a parser from a std::string because this is what i receive from a xml rpc channel. The problem is that i already have tried to use DomBuilder, MemBufInputSource with and without wrappers and i can't make it. Could someone help me with this problem, like sugesting wha

Overflow Vulnerability In SAX2Count Demo Program

Here is a patch to fix a buffer overflow in CVS revision 1.29 of samples/SAX2Count/SAX2Count.cpp. The code used strcpy() to place a user-supplied command line option into a 64-byte buffer localeStr. I've replaced this with a strncpy call instead. Yes, I know it's trivial, but it could potentially

Relative paths in C++ on Macintosh OS X

I'm having difficulty getting the Xerces-C++ parser to use relative paths on Mac OS X. Using absolute paths works fine. But when I try to pass the parser a path such as ../../../configuration.xml I get an error: The primary document entity could not be opened. Id=//../../../configuration

[jira] Commented: (XERCESC-1327) Change all enum values from ALLCAPS to MixedCase

[ http://issues.apache.org/jira/browse/XERCESC-1327?page=comments#action_60970 ] Alberto Massari commented on XERCESC-1327: -- Just adding another enum giving troubles: S_NORMAL is defined in the Win32 headers (WinBase.h) and conflicts with Regx

Re: Streaming vs. progressive XML parsing

Petar, I see no problem with streaming XML data into the Xerces SAX / DOM parser. For my purposes, I implemented a new BinInputStream along with a new InputSource. The InputSource creates an instance of this BinInputStream for the parser, and the BinInputStream provides the parser with XML data a