http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2510

*** shadow/2510 Tue Jul 10 09:20:39 2001
--- shadow/2510.tmp.29512       Tue Jul 10 15:41:45 2001
***************
*** 2,9 ****
  | traverseImport does not use parsers EntityResolver                         |
  +----------------------------------------------------------------------------+
  |        Bug #: 2510                        Product: Xerces-J                |
! |       Status: RESOLVED                    Version: 1.4.1                   |
! |   Resolution: INVALID                    Platform: All                     |
  |     Severity: Major                    OS/Version: Other                   |
  |     Priority: Other                     Component: Schema-Structures       |
  +----------------------------------------------------------------------------+
--- 2,9 ----
  | traverseImport does not use parsers EntityResolver                         |
  +----------------------------------------------------------------------------+
  |        Bug #: 2510                        Product: Xerces-J                |
! |       Status: REOPENED                    Version: 1.4.1                   |
! |   Resolution:                            Platform: All                     |
  |     Severity: Major                    OS/Version: Other                   |
  |     Priority: Other                     Component: Schema-Structures       |
  +----------------------------------------------------------------------------+
***************
*** 81,84 ****
  EntityResolver you've created--since no EntityResolver has been registered with 
  it--and so neither does Xerces or traverseImportDecl(...).  
  
! Hope that helps. :-)
--- 81,110 ----
  EntityResolver you've created--since no EntityResolver has been registered with 
  it--and so neither does Xerces or traverseImportDecl(...).  
  
! Hope that helps. :-)
! 
! ------- Additional Comments From [EMAIL PROTECTED]  2001-07-10 15:41 
-------
! No it does not help because:
! 
! I got the XMLReader interface (not object !) from the same  SAXParser created 
! before. OK i admit that setting the ErrorHandler and EntityResolver at the 
! XMLParser is better but xerces WAS able to handle that and behaved correctly 
! for that not so nice written part of the test. 
! 
! But changing it as suggested does not change the effect, it�s still there.
! 
! In both cases the EntityResolver is called by xerces for XMLSchema.xsd, 
! XMLSchema.dtd, datatypes.dtd and xml.xsd. But is is than NOT called by the 
! XMLSchema.dtd used in the xml.xsd. T
! 
! You didn�t even run the test before setting the bug to resolved invalid, did 
! you ?
! 
! The explaination for setting the bug to resolved invalid it is IMHO wrong. If  
! the EntityResolver set at the parser object instead of at the XMLReader 
! interface would not have been honored than it would also not have been called 
! for the other 4 items.
! 
! 
! 
! 

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

Reply via email to