Quick addendum to this. My <handle-error> portion calls a resource at
the end which formats the page with my application's left menu and
banner menu so I just need to fill the conent pane in with relevant
information. The first XSL the resource comes across is the
exception.xsl, which translates error:notify into the tags my
application uses. Would this lose the cocoon.session somewhere? I can
pass in variables using session-attr:attr-name from the sitemap to the
transformation, but I just can't use the ${cocoon.session.myvalue} in
any XML pages down the resource stack.
Thanks again,
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]
