Dustin N. Jenkins wrote:
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.
I guess the original request triggered flow execution? If so I suspect
handle-errors is being handled in isolated request so flow context is
not available. Thing is JXTG in 2.1.x has a different object model when
invoked from flow and standalone. This has been changed in trunk.
--
Leszek Gawron [EMAIL PROTECTED]
IT Manager MobileBox sp. z o.o.
+48 (61) 855 06 67 http://www.mobilebox.pl
mobile: +48 (501) 720 812 fax: +48 (61) 853 29 65
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
