Josh2007 wrote:
Hello,
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.
My question:
Does it mean, you can set up a session-attribute in a dependent block only
available for the time of the request? Which means if I make another request
the session-attribute 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?
Thanks,
Josh
My Cocoon blocks version:
cocoon-core: 2.2.1-SNAPSHOT
cocoon-servlet-service-components: 1.1.0-SNAPSHOT
cocoon-template-impl: 1.2.0-SNAPSHOT
cocoon-flowscript-impl: 1.1.0-SNAPSHOT
Sounds like a bug :-(
Can you file a report please?
--
Reinhard Pötz Managing Director, {Indoqa} GmbH
http://www.indoqa.com/en/people/reinhard.poetz/
Member of the Apache Software Foundation
Apache Cocoon Committer, PMC member, PMC Chair [EMAIL PROTECTED]
_________________________________________________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
