PLEASE DO NOT REPLY TO THIS MESSAGE. TO FURTHER COMMENT
ON THE STATUS OF THIS BUG PLEASE FOLLOW THE LINK BELOW
AND USE THE ON-LINE APPLICATION. REPLYING TO THIS MESSAGE
DOES NOT UPDATE THE DATABASE, AND SO YOUR COMMENT WILL
BE LOST SOMEWHERE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3134
*** shadow/3134 Tue Aug 21 12:09:40 2001
--- shadow/3134.tmp.11067 Tue Aug 28 10:30:38 2001
***************
*** 66,69 ****
passes you accordingly.
Cheers,
! Neil
--- 66,88 ----
passes you accordingly.
Cheers,
! Neil
!
! ------- Additional Comments From [EMAIL PROTECTED] 2001-08-28 10:30 -------
! Hi Neil,
!
! The issue in my use case is the fact that there's only single EntityResolver
! you can supply to the whole process of parsing/validating.
!
! I have a class which wraps around the parser and the class provides
! its own EntityResolver for resolving schemas to the parser. The user
! of the class registers its EntityResolver to the class thus the EntityResolver
! of the class essentially works as an intermediary between the parser and the
! user's EntityResolver. The intermediary gets somewhat puzzled if it gets
! relative paths because it wonders if it should try to resolve them or let
! the user's EntityResolver do it especially. If the presented systemId is
! absolute rather than relative, it would help. However, the first attempt to
! make it absolute should not fallback to the current working directory; it
! should be the very last resort.
!
! -takuki
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
