[jira] Resolved: (XERCESC-354) Exported classes with inlined virtual functions.

[ http://issues.apache.org/jira/browse/XERCESC-354?page=history ] David Bertoni resolved XERCESC-354: --- Assign To: (was: Xerces-C Developers Mailing List) Resolution: Invalid The C++ language standard specifies that inline functions have e

[jira] Closed: (XERCESC-354) Exported classes with inlined virtual functions.

[ http://issues.apache.org/jira/browse/XERCESC-354?page=history ] David Bertoni closed XERCESC-354: - > Exported classes with inlined virtual functions. > > > Key: XERCESC-354 > URL: http

[jira] Closed: (XERCESC-1214) Handle Escape Sequences Error

[ http://issues.apache.org/jira/browse/XERCESC-1214?page=history ] David Bertoni closed XERCESC-1214: -- > Handle Escape Sequences Error > - > > Key: XERCESC-1214 > URL: http://issues.apache.org/jira/browse/X

[jira] Resolved: (XERCESC-1214) Handle Escape Sequences Error

[ http://issues.apache.org/jira/browse/XERCESC-1214?page=history ] David Bertoni resolved XERCESC-1214: Resolution: Invalid I attempted to reproduce what you claim to observe but cannot. I think you may not understand how SAX parsing works, be

[jira] Resolved: (XERCESC-976) ReaderMgr may delete fCurReader twice

[ http://issues.apache.org/jira/browse/XERCESC-976?page=history ] David Bertoni resolved XERCESC-976: --- Assign To: (was: Xerces-C Developers Mailing List) Resolution: Fixed Fix Version: 2.6.0 I'm not sure when this was fixed, but it'

[jira] Closed: (XERCESC-1334) XMLTransService::makeNewTranscoderFor(...) does not have a corresponding method to release the memory it allocates. Once a new XMLTranscoder is created, no other feasible way to clear up the memory except for calling XMLTranscoder destructor explicitly

[ http://issues.apache.org/jira/browse/XERCESC-1334?page=history ] David Bertoni closed XERCESC-1334: -- > XMLTransService::makeNewTranscoderFor(...) does not have a corresponding > method to release the memory it allocates. Once a new XMLTranscoder is

[jira] Commented: (XERCESC-1368) Catch-all handler are problematic on Windows

[ http://issues.apache.org/jira/browse/XERCESC-1368?page=comments#action_62390 ] David Bertoni commented on XERCESC-1368: I am attaching a patch that contains a new proposed class implemented in Janitor.h and Janitor.c. The patch also contains

[jira] Closed: (XERCESC-976) ReaderMgr may delete fCurReader twice

[ http://issues.apache.org/jira/browse/XERCESC-976?page=history ] David Bertoni closed XERCESC-976: - > ReaderMgr may delete fCurReader twice > - > > Key: XERCESC-976 > URL: http://issues.apache.org/j

[jira] Commented: (XERCESC-1377) Error in SAXParser! invalid namespaces

[ http://issues.apache.org/jira/browse/XERCESC-1377?page=comments#action_62394 ] David Bertoni commented on XERCESC-1377: I believe, per the reporter's email to the list, that this is not bug in the SAXParser class, since it does not support na

[jira] Assigned: (XERCESC-1368) Catch-all handler are problematic on Windows

[ http://issues.apache.org/jira/browse/XERCESC-1368?page=history ] David Bertoni reassigned XERCESC-1368: -- Assign To: David Bertoni > Catch-all handler are problematic on Windows > > > Key: XERCE

[jira] Updated: (XERCESC-1368) Catch-all handler are problematic on Windows

[ http://issues.apache.org/jira/browse/XERCESC-1368?page=history ] David Bertoni updated XERCESC-1368: --- Attachment: patch.txt > Catch-all handler are problematic on Windows > > > Key: XERCESC-1368 >

[jira] Resolved: (XERCESC-1334) XMLTransService::makeNewTranscoderFor(...) does not have a corresponding method to release the memory it allocates. Once a new XMLTranscoder is created, no other feasible way to clear up the memory except for calling XMLTranscoder destructor explicitly

[ http://issues.apache.org/jira/browse/XERCESC-1334?page=history ] David Bertoni resolved XERCESC-1334: Resolution: Invalid > XMLTransService::makeNewTranscoderFor(...) does not have a corresponding > method to release the memory it allocates.

[jira] Commented: (XERCESC-1021) RegularExpression: wrong Match end for fixed string match

[ http://issues.apache.org/jira/browse/XERCESC-1021?page=comments#action_62386 ] David Bertoni commented on XERCESC-1021: Is there any chance you can provide some sample input (regular expression, string to match) and the expected output to inv

Re: New make output

Gareth Reakes wrote: > Hi Axel, > > We are currently moving over to configure / make / make install > model. We should probably wait until that has finished to see if the > changes would still make sense. Would you like to help out with that? Hi Gareth, you mean, you want to get rid of the

[jira] Commented: (XERCESC-1401) Not documented xerces-c exception: DOMNode::appendChild

[ http://issues.apache.org/jira/browse/XERCESC-1401?page=comments#action_62370 ] David Bertoni commented on XERCESC-1401: The fact that your catch(...) handler catches an access violation is a property of Microsoft's asynchronous exception mode

[jira] Commented: (XERCESC-1403) Compilation error using the Xcerces

[ http://issues.apache.org/jira/browse/XERCESC-1403?page=comments#action_62369 ] David Bertoni commented on XERCESC-1403: Did you even read the compiler diagnostics you posted? > "/include/xcerces/xercesc/framework/XMLErrorReporter.hpp", line

Re: New make output

Hi Axel, We are currently moving over to configure / make / make install model. We should probably wait until that has finished to see if the changes would still make sense. Would you like to help out with that? Cheers, Gareth Axel Weiß wrote: Am Dienstag, 5. April 2005 11:21 schrieb Gareth Rea

[jira] Resolved: (XERCESC-1401) Not documented xerces-c exception: DOMNode::appendChild

[ http://issues.apache.org/jira/browse/XERCESC-1401?page=history ] Alberto Massari resolved XERCESC-1401: -- Resolution: Fixed A fix is in CVS. Please verify Alberto > Not documented xerces-c exception: DOMNode::appendChild > --

[jira] Commented: (XERCESC-1403) Compilation error using the Xcerces

[ 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 happens if you build the

[jira] Commented: (XERCESC-1403) Compilation error using the Xcerces

[ http://issues.apache.org/jira/browse/XERCESC-1403?page=comments#action_62355 ] Praveen Maruvekere commented on XERCESC-1403: - Well, I am vrey much sure that I am not using any macro called "error" The header file "XMLErrorReporter.hpp" has

RE: control characters in the Xml

OK, It just seemed a bit hacky to be messing with the document in memory so I thought I'd check in case I was missing something obvious Thanks for the help Vin > -Original Message- > From: Tony Dodd [mailto:[EMAIL PROTECTED] > Sent: 07 April 2005 08:06 > To: xerces-c-dev@xml.apac

Re: URLInputSource or LocalFileInputSource fails under cygwin

Axel, my answer is below. > Am Mittwoch, 6. April 2005 20:48 schrieb Ovanes Markarian: > > Hi all! > > > > I am trying to open a local file under cygwin using either the URI or > > local unix name for it. Under Win32 (XP) this code works fine, but > > under Cygwin it fails. I tried a lot of appro

Re: URLInputSource or LocalFileInputSource fails under cygwin

Am Mittwoch, 6. April 2005 20:48 schrieb Ovanes Markarian: > Hi all! > > I am trying to open a local file under cygwin using either the URI or > local unix name for it. Under Win32 (XP) this code works fine, but > under Cygwin it fails. I tried a lot of approaches, like splitting > the path into th

[jira] Commented: (XERCESC-1401) Not documented xerces-c exception: DOMNode::appendChild

[ http://issues.apache.org/jira/browse/XERCESC-1401?page=comments#action_62340 ] Sergiy Michka commented on XERCESC-1401: I found what cause the undocumented exception. To reproduce this in CreateDOMDocument xerces-c Sample project: File: Crea

[jira] Commented: (XERCESC-1403) Compilation error using the Xcerces

[ http://issues.apache.org/jira/browse/XERCESC-1403?page=comments#action_62335 ] David Bertoni commented on XERCESC-1403: Your code, or some code you are including defines a macro called "error", which is both incompatible with Xerces-C and a b

Re: Xerces-C migration from CVS to SVN

Hi Jason, Gareth's bug is here: http://issues.apache.org/jira/browse/INFRA-266 The infrastruture JIRA database is here: http://issues.apache.org/jira/secure/BrowseProject.jspa?id=10410 Dave [EMAIL PROTECTED] (Jason E. Stewart) Sent by: "Jason E. Stewart" <[EMAIL PROTECTED]> 04/06/2005 10:

RE: control characters in the Xml

I don't think there is another way. It doesn't seem like a hack to me! The DomDocument set version function is for when you want to build a document in memory. The document is then correctly serialised with a 1.1 XML declaration. But I don't see how that would help with parsing. Tony >-Orig