[
https://issues.apache.org/jira/browse/COCOON-2044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Klimetschek updated COCOON-2044:
------------------------------------------
Priority: Critical (was: Major)
Description:
All servlet protocol URIs like servlet:/some/thing or servlet:super:/foo/bar or
servlet:myblock:/another/path have to be globally unique because they are used
in the cache, of which there is only one global with globally acting keys.
There are two caches in standard Cocoon configuration (the only ones I know of
;-), both with a different key generation. Here are ideas how to make the keys
global:
a) EHDefaultStore for caching resources of caching pipelines: they use the
uriPrefix of the Enviroment in the key, so providing a uriPrefix (eg. the mount
path of the servlet) works here.
b) DefaultTransientStore which caches XSLT and JX generator sources (don't know
why this is different from a)): they do not use the uriPrefix and much worse,
they need correct URIs because they are read by the XSLT processor, who does
not like things like servlet:uniqueID34:/xsl/stylesheet.xsl containing
arbitrary schemes at the beginning. Appending an ID via a query parameter seems
the only working solution (tried it already):
servlet:/xsl/stylesheet.xsl?servlet-services-id=12345
Another solution would be to have one cache per sitemap, so that the keys don't
have to be unique anymore. But I don't know how to configure that and if this
is feasible.
<old_issue_description>
The call to servlet:/something fails on the first attempt, the effect is an
empty output stream. After a reload it mostly works, but I cannot yet give
exact behaviour as I am still debugging the problem.
It seems to be related to the caching (because it works on the second attemp),
but it also happens in a NonCachingProcessingPipeline.
</old_issue_description>
was:
The call to servlet:/something fails on the first attempt, the effect is an
empty output stream. After a reload it mostly works, but I cannot yet give
exact behaviour as I am still debugging the problem.
It seems to be related to the caching (because it works on the second attemp),
but it also happens in a NonCachingProcessingPipeline.
Urgency: Normal
Summary: servlet: protocol URIs are have to be globally unique for use
as cache-keys (was: Servlet services calls to servlet: sometimes fail (on
initial call))
Found out the real problem, thus I changed the summary and the description of
this issue: the *local* servlet: calls (without a servlet name in the URI,
acting like cocoon:) fail in certain situations when there are two identical
URIs in two blocks (eg. servlet:/xslt/html2html.xsl) but the resource will be
cached globally under the same name.
> servlet: protocol URIs are have to be globally unique for use as cache-keys
> ---------------------------------------------------------------------------
>
> Key: COCOON-2044
> URL: https://issues.apache.org/jira/browse/COCOON-2044
> Project: Cocoon
> Issue Type: Bug
> Components: - Servlet service framework
> Affects Versions: 2.2-dev (Current SVN)
> Reporter: Alexander Klimetschek
> Priority: Critical
>
> All servlet protocol URIs like servlet:/some/thing or servlet:super:/foo/bar
> or servlet:myblock:/another/path have to be globally unique because they are
> used in the cache, of which there is only one global with globally acting
> keys.
> There are two caches in standard Cocoon configuration (the only ones I know
> of ;-), both with a different key generation. Here are ideas how to make the
> keys global:
> a) EHDefaultStore for caching resources of caching pipelines: they use the
> uriPrefix of the Enviroment in the key, so providing a uriPrefix (eg. the
> mount path of the servlet) works here.
> b) DefaultTransientStore which caches XSLT and JX generator sources (don't
> know why this is different from a)): they do not use the uriPrefix and much
> worse, they need correct URIs because they are read by the XSLT processor,
> who does not like things like servlet:uniqueID34:/xsl/stylesheet.xsl
> containing arbitrary schemes at the beginning. Appending an ID via a query
> parameter seems the only working solution (tried it already):
> servlet:/xsl/stylesheet.xsl?servlet-services-id=12345
> Another solution would be to have one cache per sitemap, so that the keys
> don't have to be unique anymore. But I don't know how to configure that and
> if this is feasible.
> <old_issue_description>
> The call to servlet:/something fails on the first attempt, the effect is an
> empty output stream. After a reload it mostly works, but I cannot yet give
> exact behaviour as I am still debugging the problem.
> It seems to be related to the caching (because it works on the second
> attemp), but it also happens in a NonCachingProcessingPipeline.
> </old_issue_description>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
