Joe,

I believe that this is defect #2195.  The good news is that it was
fixed on Oct 3 and should appear in the next Beta.  Considering that
I opened the defect against the Alpha release back in June, and had
included the fix at that time, I guess that I am somewhat saddened
by the fact that you have had to deal with this.  I am also quite
amused that the defect was resolved as fixed on Sept. 9, almost a
month before the code was actually modified.

Come on folks, is this really the best that we can do?

-Glenn



                                                                                       
                        
                    Joseph                                                             
                        
                    Kesselman/CAM/L       To:     [EMAIL PROTECTED]          
                        
                    otus@Lotus            cc:                                          
                        
                                          Subject:     Re: Interested in getting 
changes into main Xerces      
                    10/17/2001             distribution                                
                        
                    05:28 PM                                                           
                        
                    Please respond                                                     
                        
                    to xerces-j-dev                                                    
                        
                                                                                       
                        
                                                                                       
                        





I seem to have exposed a parser bug in Xerces 2_0_0_beta2.  Run the
attached application through sax.Writer. Look at the attributes on the
<xsl:element/> -- one missing, one replicated.

(Note too that the namespace declaration isn't passed through, though
apparently that's a serializer behavior rather than something happening in
the parser. I'm not convinced that's a _good_ behavior, but it's
justifiable, especially since setting a namespace URI to "" isn't really
supported anyway, with the one exception of "undefining" the default
namespace.)


I seem to remember someone else recently reporting something similar. Is
this a known glitch, already fixed, or should I file a Bugzilla entry on
it?

(See attached file: namespace85.xsl)

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

#### namespace85.xsl has been removed from this note on October 18 2001 by
Glenn Marcy




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to