Enrique Perez wrote:
Hi all,
I have two portlets. In the first one we can choose one of several
actions available (by clicking one or another button), and the other one
process the action requested.
At the beginning, everything seems to work fine... but if I don't click
any button (in the first portlet) for a few time, when I click any
button again I get this message in the second portlet:
Portlet is Not Available: Test_1::portlet-2
Reason: Cannot call getRequestContext(HttpServletRequest request)
before it has been created and set for this thread.
But then I click again and that exception disappears and everything
seems to work fine (as if any exception had occurred).
This second portlet just reads a request attribute from portlet session
(with application scope). It's like the second portlet can't render well
if it's been inactive for too long.
Ive seen that one once, but then I could not reproduce it, as it seems
very intermittent. Let us know if you have a reproducible test case,
that would help
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
