[jira] [Updated] (JS2-1323) ActionResponse.setRenderParameter crashes ActionUrl ?

     [ https://issues.apache.org/jira/browse/JS2-1323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Maidhof updated JS2-1323:
--------------------------------
    Description: 
Is it possible, that setRenderParameter in one portlet crashes the action url in another portlet on the same page ?

We have the following scenario:

- 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 !

Here are our jetspeed settings (override.properties). We use PSML in the database:

merge.portal.parameters.with.portlet.parameters=true
merge.portal.parameters.before.portlet.parameters=true
portalurl.relative.only=false
portal.statistics.logToDatabase=false
portal.audit.enable=false
psml.template.folder = /_user/template/
jetui.customization.method = server

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

We have the following scenario:

- 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 !

Here are our jetspeed settings (override.properties). We use PSML in the database:

# Use this to override settings in jetspeed.properties
merge.portal.parameters.with.portlet.parameters=true
merge.portal.parameters.before.portlet.parameters=true
portalurl.relative.only=false
portal.statistics.logToDatabase=false
portal.audit.enable=false
psml.template.folder = /_user/template/
jetui.customization.method = server


> ActionResponse.setRenderParameter crashes ActionUrl ?
> -----------------------------------------------------
>
>                 Key: JS2-1323
>                 URL: https://issues.apache.org/jira/browse/JS2-1323
>             Project: Jetspeed 2
>          Issue Type: Bug
>          Components: Components Core
>    Affects Versions: 2.3.0
>         Environment: Windows 7, Tomcat 7.0.56, Java 1.8.0_25, MySQL 5.5.8
>            Reporter: Martin Maidhof
>             Fix For: 2.3.0
>
>
> Is it possible, that setRenderParameter in one portlet crashes the action url in another portlet on the same page ?
> We have the following scenario:
> - 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 !
> Here are our jetspeed settings (override.properties). We use PSML in the database:
> merge.portal.parameters.with.portlet.parameters=true
> merge.portal.parameters.before.portlet.parameters=true
> portalurl.relative.only=false
> portal.statistics.logToDatabase=false
> portal.audit.enable=false
> psml.template.folder = /_user/template/
> jetui.customization.method = server



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)