[
https://issues.apache.org/jira/browse/COCOON-2010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grzegorz Kossakowski (aka g[R]eK) updated COCOON-2010:
------------------------------------------------------
Attachment:
cocoon-servlet-service-components-servletSource-workingValidity-patch-1.txt
cocoon-servlet-service-components-servletSource-workingValidity-patch-1.txt:
This patch implements properly working validity for ServletSource. It was
discussed here how it should work:
http://news.gmane.org/find-root.php?group=gmane.text.xml.cocoon.devel&article=70383
I've put important comment explaining why ServletValidity stores
ServletConnection. I only wonder if it's safe to store reference to the
ServletConnection on long term. However, I do not know how to clear this
reference at the end of request processing. It would be possible to clear it in
isValid method but is there any guarantee that this method will be called only
once?
> ServletConnection and ServletSource cache-aware
> -----------------------------------------------
>
> Key: COCOON-2010
> URL: https://issues.apache.org/jira/browse/COCOON-2010
> Project: Cocoon
> Issue Type: Improvement
> Components: - Blocks Framework
> Affects Versions: 2.2-dev (Current SVN)
> Reporter: Grzegorz Kossakowski (aka g[R]eK)
> Fix For: 2.2-dev (Current SVN)
>
> Attachments:
> cocoon-servlet-service-components-servletSource-workingValidity-patch-1.txt,
> cocoon-servlet-service-impl-servletConnection-cache-aware-patch-1.txt
>
>
> As discussed here:
> http://news.gmane.org/find-root.php?group=gmane.text.xml.cocoon.devel&article=70383
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
