RE: Xerces 2.2.1
It works with Xerces 2.2.1. I'll close all the bugs (Xalan & FOP) marked as Invalid. Thanks, Bernard -Original Message- From: Peter B. West [mailto:[EMAIL PROTECTED]] Sent: 20 November, 2002 0:38 To: [EMAIL PROTECTED] Subject: Re: Xerces 2.2.1 Bernard, Ah, memory! Wonderful thing when it works. I must remember to read Proust again. I wanted to talk to you about this. I haven't yet followed up on your fix to this, so I am not sure how you handle it, but wouldn't the variable and the process be better as startDocumentAlreadySeen? Then you can skip the whole STARTDOCUMENT handler if the variable is true. Have you tried the original code with 2.2.1? Peter Bernard D'Have wrote: > It's me. > It is bug 14539 in Bugzilla. > > It's just that in you have a comment before the root element, the SAX > startDocument is called two times. - This mail was sent through webmail.wanadoo.be - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Xerces 2.2.1
Bernard, Ah, memory! Wonderful thing when it works. I must remember to read Proust again. I wanted to talk to you about this. I haven't yet followed up on your fix to this, so I am not sure how you handle it, but wouldn't the variable and the process be better as startDocumentAlreadySeen? Then you can skip the whole STARTDOCUMENT handler if the variable is true. Have you tried the original code with 2.2.1? Peter Bernard D'Have wrote: It's me. It is bug 14539 in Bugzilla. It's just that in you have a comment before the root element, the SAX startDocument is called two times. -- Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwest/ "Lord, to whom shall we go?" - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: Xerces 2.2.1
I'll check this tomorrow at work. Bernard > -Original Message- > From: Jeremias Maerki [mailto:[EMAIL PROTECTED]] > Sent: 19 November, 2002 20:28 > To: [EMAIL PROTECTED] > Subject: Re: Xerces 2.2.1 > > > So, could you check if the problem persist when using a Xerces 2.2.1? > Thanks. > > On 19.11.2002 20:10:30 Bernard D'Have wrote: > > It's me. > > It is bug 14539 in Bugzilla. > > > > It's just that in you have a comment before the root element, the SAX > > startDocument is called two times. > > > Jeremias Maerki > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, email: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Xerces 2.2.1
So, could you check if the problem persist when using a Xerces 2.2.1? Thanks. On 19.11.2002 20:10:30 Bernard D'Have wrote: > It's me. > It is bug 14539 in Bugzilla. > > It's just that in you have a comment before the root element, the SAX > startDocument is called two times. Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: Xerces 2.2.1
It's me. It is bug 14539 in Bugzilla. It's just that in you have a comment before the root element, the SAX startDocument is called two times. Bernard > -Original Message- > From: Peter B. West [mailto:[EMAIL PROTECTED]] > Sent: 19 November, 2002 15:44 > To: [EMAIL PROTECTED] > Subject: Re: Xerces 2.2.1 > > > Jeremias Maerki wrote: > > Hi Peter > > > > I should have done that earlier because about at the same time I updated > > to Xerces 2.2.0, Xerces 2.2.1 was published and I knew it was a bugfix > > release. > > > > On 19.11.2002 15:18:45 Peter B. West wrote: > > > >>I'm glad to see that you have upgraded Xerces to 2.2.1. I just > >>discovered that 2.2.0 was badly broken when my code fell over after I > >>had upgraded to that release. Unfortunately I had also made a > number of > >>code changes at the same time (bad practice), so it took a > while to work > >>out what was going on. > >> > >>This may fix some problems that have been attributed to Xalan. > > > > > > Which, if I may ask? > > Nothing in particular. I just remembered that someone recently posted a > bug report to Xalan. Bugs in Xerces could well have ramifications for > Xalan. > > Peter > -- > Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwest/ > "Lord, to whom shall we go?" > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, email: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Xerces 2.2.1
Jeremias Maerki wrote: Hi Peter I should have done that earlier because about at the same time I updated to Xerces 2.2.0, Xerces 2.2.1 was published and I knew it was a bugfix release. On 19.11.2002 15:18:45 Peter B. West wrote: I'm glad to see that you have upgraded Xerces to 2.2.1. I just discovered that 2.2.0 was badly broken when my code fell over after I had upgraded to that release. Unfortunately I had also made a number of code changes at the same time (bad practice), so it took a while to work out what was going on. This may fix some problems that have been attributed to Xalan. Which, if I may ask? Nothing in particular. I just remembered that someone recently posted a bug report to Xalan. Bugs in Xerces could well have ramifications for Xalan. Peter -- Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwest/ "Lord, to whom shall we go?" - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Xerces 2.2.1
Hi Peter I should have done that earlier because about at the same time I updated to Xerces 2.2.0, Xerces 2.2.1 was published and I knew it was a bugfix release. On 19.11.2002 15:18:45 Peter B. West wrote: > I'm glad to see that you have upgraded Xerces to 2.2.1. I just > discovered that 2.2.0 was badly broken when my code fell over after I > had upgraded to that release. Unfortunately I had also made a number of > code changes at the same time (bad practice), so it took a while to work > out what was going on. > > This may fix some problems that have been attributed to Xalan. Which, if I may ask? Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
