http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2529
*** shadow/2529 Fri Jul 13 05:43:48 2001
--- shadow/2529.tmp.8874 Fri Jul 13 16:20:07 2001
***************
*** 2,9 ****
| URI resolving of imported namespaces is not correct |
+----------------------------------------------------------------------------+
| Bug #: 2529 Product: Xerces-J |
! | Status: REOPENED Version: 1.4.1 |
! | Resolution: Platform: PC |
| Severity: Blocker OS/Version: Windows NT/2K |
| Priority: High Component: Schema-Structures |
+----------------------------------------------------------------------------+
--- 2,9 ----
| URI resolving of imported namespaces is not correct |
+----------------------------------------------------------------------------+
| Bug #: 2529 Product: Xerces-J |
! | Status: RESOLVED Version: 1.4.1 |
! | Resolution: WORKSFORME Platform: PC |
| Severity: Blocker OS/Version: Windows NT/2K |
| Priority: High Component: Schema-Structures |
+----------------------------------------------------------------------------+
***************
*** 47,50 ****
Regards
! Thomas
--- 47,74 ----
Regards
! Thomas
!
! ------- Additional Comments From [EMAIL PROTECTED] 2001-07-13 16:20
-------
! The resolveEntity method will always be called with an absolute URI when you
! gave the parser a chance to have some absolute base URI for creating absolute
! URI's from relative ones.
!
! If you use parse(String systemId) you should supply an absolute URI.
!
! If you use parse(InputSource input) you can use setSystemId at the InputSource
! to set the absolute URI.
!
! What you will most likely do in such EntityResolver is either keeping some
! hashtables of public and system identifiers to 'real' locations and than return
! an InputSource created from that 'real' location. For doing this xerces
! contains an nice base class org.apache.readers.XMLCatalogHandler and the
! XCatalog that can load such mappings from a file using an xml based format.
!
! You can also use the EntityResolver to handle your own
! vnd.mycompany.myscheme:/.. URI scheme(s) or do both, eg. if you created the
! InputStream using some application specific procedure that doesn�t map to the
! URI schemes known to xerces like file:// http://.
!
! For resolving relative to absolute URI�s have a look at the java.net.URI class
! in JDK1.4 and http://www.ietf.org/rfc/rfc2396.txt
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
