http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2124 *** shadow/2124 Tue Jun 12 00:04:22 2001 --- shadow/2124.tmp.3468 Tue Jun 12 00:04:22 2001 *************** *** 0 **** --- 1,33 ---- + +============================================================================+ + | Status of SAXSource is changed in Xalan 2.1.0 | + +----------------------------------------------------------------------------+ + | Bug #: 2124 Product: XalanJ2 | + | Status: NEW Version: 2.0.x | + | Resolution: Platform: PC | + | Severity: Normal OS/Version: Windows NT/2K | + | Priority: Other Component: javax.xml | + +----------------------------------------------------------------------------+ + | Assigned To: [EMAIL PROTECTED] | + | Reported By: [EMAIL PROTECTED] | + | CC list: Cc: | + +----------------------------------------------------------------------------+ + | URL: | + +============================================================================+ + | DESCRIPTION | + Hi, + + may be I am absolutely wrong. But in my opinion the method: + public SAXSource(XMLReader reader, + InputSource inputSource) is designed to use a + XMLReader with predefined settings. + For the xerces parser these settings are changed because dynamic validation + is switched on. + So if there is only a DTD subset for defaulting attributes the transformation + will fail. + On the other hand Xerces 1.4 offers a beta XML Schema support. The setting + features does not work correct at the time. But with a predefined XMLReader it + is possible to create workarounds if the settings are not changed. + + Regards, + + Thomas \ No newline at end of file
