[ https://issues.apache.org/jira/browse/COCOON-2194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Josh updated COCOON-2194: ------------------------- Summary: Session-attr set in dependency blocks destroyed after servlet call. (was: Session-attr set in dependency blocks systematically destroyed after servlet call.) > Session-attr set in dependency blocks destroyed after servlet call. > ------------------------------------------------------------------- > > Key: COCOON-2194 > URL: https://issues.apache.org/jira/browse/COCOON-2194 > Project: Cocoon > Issue Type: Bug > Components: * Cocoon Core, - Servlet service framework > Affects Versions: 2.2-dev (Current SVN) > Reporter: Josh > > I have a main block (block-a) which makes calls to a depend block (block-b). > Block-b has access to the global session. > At the first call from block-a, block-b creates a session-attribute "test". > I noticed this session-attribute can be retrieved within block-b (right after > setting it), but not within block-a. > At the second call from block-a, block-b needs to read the session-attribute > "test" it has created at the first call, but cannot find it anymore: > session-attr "test" doesn't exists. > It seems session-attributes set up in a dependency block are only available > for the time of the request. This means if any other request to the block is > made, the session-attributes will not be available anymore. > Is there a way to set a session-attribute in a dependent block and make it > available for the duration of the global session? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.