BUG ?: actionResponse.setRenderParameter crashes ActionUrl ???

Hi all,

we recently experienced the following strange behavior using the current
Jetspeed trunk in our portal:


- PORTLET A and PORTLET B on same page, both with forms and action url
in the velocity template like:
#set ($action = $renderResponse.createActionURL())
$action.setParameter('action','doSearch')
<form action="$action" ...

- PORTLET B sets a Render Parameter in its processAction():
    actionResponse.setRenderParameter("cmd", action);

- PORTLET A nd B are rendered, PORTLET B picks up the render parameter, ok

- BUT: On button click in PORTLET A the processAction() method of
PORTLET A is NOT called anymore !
Instead PORTLET A only enters it's doView method in the render phase.

If PORTLET B does NOT set the render parameter then PORTLET A calls it's
action method properly !


Is it possible, that setRenderParameter in one portlet crashes the
action url in another portlet on the same page ?

We migrated our portal to the current jetspeed trunk using the most
recent snapshots.
But the methods we use are nearly all still JSR 168 compliant (where no
compiler errors occured).

I think actionResponse.setRenderParameter should still be valid in JSR 286 ?
Can you verify this strange behavior ?

Thanks for any help !
best regards,
    Martin