You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xalan.apache.org by bu...@apache.org on 2001/03/09 05:47:01 UTC

[Bug 906] Changed - customized URIResolver doesn't process xsl:include correctly

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

*** shadow/906	Thu Mar  8 13:12:30 2001
--- shadow/906.tmp.29951	Thu Mar  8 20:47:01 2001
***************
*** 2,11 ****
  | customized URIResolver doesn't process xsl:include correctly               |
  +----------------------------------------------------------------------------+
  |        Bug #: 906                         Product: XalanJ2                 |
! |       Status: UNCONFIRMED                 Version: 2.0.0                   |
  |   Resolution:                            Platform: PC                      |
! |     Severity: Normal                   OS/Version:                         |
! |     Priority: Medium                    Component: javax.xml               |
  +----------------------------------------------------------------------------+
  |  Assigned To: xalan-dev@xml.apache.org                                     |
  |  Reported By: cao@ispsoft.com                                              |
--- 2,11 ----
  | customized URIResolver doesn't process xsl:include correctly               |
  +----------------------------------------------------------------------------+
  |        Bug #: 906                         Product: XalanJ2                 |
! |       Status: ASSIGNED                    Version: 2.0.0                   |
  |   Resolution:                            Platform: PC                      |
! |     Severity: Major                    OS/Version: All                     |
! |     Priority: High                      Component: javax.xml               |
  +----------------------------------------------------------------------------+
  |  Assigned To: xalan-dev@xml.apache.org                                     |
  |  Reported By: cao@ispsoft.com                                              |
***************
*** 62,65 ****
          e.printStackTrace();
        }
      }
! }
--- 62,94 ----
          e.printStackTrace();
        }
      }
! }
! 
! ------- Additional Comments From scott_boag@lotus.com  2001-03-08 20:47 -------
! Guoliang, where did you get the parameters for URIResolver#Resolve?  They 
! should be:
! 
!     /**
!      * Called by the processor when it encounters
!      * an xsl:include, xsl:import, or document() function.
!      *
!      * @param href An href attribute, which may be relative or absolute.
!      * @param base The base URI in effect when the href attribute
!      * was encountered.
!      *
!      * @return A Source object, or null if the href cannot be resolved,
!      * and the processor should try to resolve the URI itself.
!      *
!      * @throws TransformerException if an error occurs when trying to
!      * resolve the URI.
!      */
!     public Source resolve(String href, String base)
!         throws TransformerException;
! 
! i.e. you have resolve(String publicId, String systemId).  Is there a mismatch 
! with some other version of URIResolver floating around?  Anyway, I think that 
! is the root of your problem... you should be testing the first argument, not 
! the second.
! 
! I did find a bug.  The base should be absolutized if the including stylesheet 
! was a relative URL, and it is not.  I am working on this problem.