I wasted twenty-six hours trying to get this straightened out, so here's
the solution so nobody else will have to. Instead of using
${cocoon.session.blah}, I had to change it to
${session.getAttribute('blah')}. For some reason the cocoon.session
context is lost. Is this a bug? I tried the latest BRANCH_2_1_X and
the problem was there too.
Cheers,
Dustin
Dustin N. Jenkins wrote:
Whenever I throw a custom RuntimeException and catch it using the
<handle-errors> tag, it loses the HTTP session information (i.e. I
can't use the ${cocoon.session.XXX} in any of my following XML
files). Is there any way to preserve it?
Thanks,
Dustin
--
Dustin N. Jenkins
Application Developer
Invoq Systems, Inc.
AlarmPoint - Guaranteed Event Resolution
#216 - 852 Fort Street
Victoria, BC V8W 1H8
Tel: (250) 380-0304
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
http://www.invoqsystems.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
