cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ard Schrijvers (JIRA)" <j...@apache.org>
Subject [jira] Commented: (COCOON-1909) Cache validity of XSLT stylesheets does not reflect included or imported stylesheets.
Date Thu, 12 Oct 2006 09:27:36 GMT
    [ http://issues.apache.org/jira/browse/COCOON-1909?page=comments#action_12441677 ] 
            
Ard Schrijvers commented on COCOON-1909:
----------------------------------------

The bug is in XSLTProcessorImpl in public javax.xml.transform.Source resolve( String href,
String base ), at List includes = (List)m_includesMap.get( base );. The problem lies in the
"base", because the base is related to the stylesheet "calling" the import, so, if it is an
import calling an import, the "base" is different from the main stylesheet, therefor not adding
its validity to the main stylesheet aggregated validity.

I added a global "m_id" of the main stylesheet that is now used in XSLTProcessorImpl, and
replace "base" in List includes = (List)m_includesMap.get( base ) by List includes = (List)m_includesMap.get(
m_id );. This solves the invalidation of main stylesheets.

The bug is solved when a new xmlutil jar is included in cocoon

> Cache validity of XSLT stylesheets does not reflect included or imported stylesheets.
> -------------------------------------------------------------------------------------
>
>                 Key: COCOON-1909
>                 URL: http://issues.apache.org/jira/browse/COCOON-1909
>             Project: Cocoon
>          Issue Type: Bug
>          Components: - Components: Sitemap
>    Affects Versions: 2.1.9
>            Reporter: Conal Tuohy
>
> XSLT stylesheets which either import or include other stylesheets are cached too aggressively:
if you change an imported or included stylesheet the change does not take effect until you
update the main stylesheet.
> This bug is supposed to have been fixed years ago, but it still doesn't work for us.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message