Thank you very much for the lesson. I'll try another way.
Roman
Vadim Gritsenko wrote:
> > From: KOZLOV Roman [mailto:[EMAIL PROTECTED]]
> >
> > Hello,
> >
> > Vadim thank you for your advice. It helped me. I was busy some
> time and
> > had postponed this problem. Unfortunatelly it stil
> From: KOZLOV Roman [mailto:[EMAIL PROTECTED]]
>
> Hello,
>
> Vadim thank you for your advice. It helped me. I was busy some
time and
> had postponed this problem. Unfortunatelly it still remains.
> I've found out that WildcardSessionAttributeMatcher (I'm using
Cocoon
> 2.0.1) doesn't s
Hello,
Vadim thank you for your advice. It helped me. I was busy some time and
had postponed this problem. Unfortunatelly it still remains.
I've found out that WildcardSessionAttributeMatcher (I'm using Cocoon
2.0.1) doesn't see session attributes changed or created before in the same
req
Roman,
Aggregation is being executed linearly, which means that first part is
executed before second. If first part contains an XSP and that XSP is
not cached, it could change session attribute which will be visible in
the second part's XSP (if it is not cached)
XSPs are not cacheable by default
