Re: Xalan-C 1.4 seems to report style nodes to problem listeners lessfaithfully

[David N Bertoni/Cambridge/IBM]

Yes, one was sacrificed for the other.  It's possible to do both, so if you
need it, file an enhancement in Bugzilla.  I can't promise when I can get
to it, but it wouldn't be too hard to do.

Dave



                                                                                       
                                               
                      Brian Quinlan                                                    
                                               
                      <brian@sweetapp.         To:      [EMAIL PROTECTED]       
                                               
                      com>                     cc:      (bcc: David N 
Bertoni/Cambridge/IBM)                                          
                                               Subject: Xalan-C 1.4 seems to report 
style nodes to problem listeners less faithfully  
                      09/22/2002 04:05                                                 
                                               
                      PM                                                               
                                               
                      Please respond                                                   
                                               
                      to xalan-dev                                                     
                                               
                                                                                       
                                               
                                                                                       
                                               



In Xalan-C 1.3, usage of an undefined variable causes the
ProblemListener to be called with a valid style node. In Xalan-C 1.4,
the style node passed to the ProblemListener is NULL.

The same is true of messages generated using xsl:message.

Is this a bug or a feature that has been deliberately removed?

OTOH, the URI and locator information passed to the ProblemListener are
now more accurate :-)

Cheers,
Brian