[prev in list] [next in list] [prev in thread] [next in thread] 

List:       myfaces-dev
Subject:    [jira] Resolved: (MYFACES-1311) MyFaces Portlet at Weblogic 8.1
From:       "Martin Marinschek (JIRA)" <dev () myfaces ! apache ! org>
Date:       2007-09-28 16:06:50
Message-ID: 11222108.1190995610711.JavaMail.jira () brutus
[Download RAW message or body]


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

Martin Marinschek resolved MYFACES-1311.
----------------------------------------

       Resolution: Later
    Fix Version/s: 1.1.6
         Assignee: Martin Marinschek

This sounds like a problem in the portlet-bridge. Please try again with the JSR-301 \
implementation and then tell us what the outcome was.

regards,

Martin

> MyFaces Portlet at Weblogic 8.1 SP5: Request Parameter weren't submitted
> ------------------------------------------------------------------------
> 
> Key: MYFACES-1311
> URL: https://issues.apache.org/jira/browse/MYFACES-1311
> Project: MyFaces Core
> Issue Type: Bug
> Affects Versions: 1.1.1, 1.1.3
> Environment: Win XP,  jdk 1.4.2, Weblogic 8.1 SP 5 Portal Server, MyFacesPortlet, \
>                 Tested with MyFaces 1.1.1 and MyFaces 1.1.3
> Reporter: Stefan Gesigora
> Assignee: Martin Marinschek
> Priority: Critical
> Fix For: 1.1.6
> 
> 
> While using MyFaces in a portlet at the Weblogic 8.1 SP5 Portal Server the \
> navigation doesn't work in the right way: per \
> "FacesContext.getCurrentInstance().getExternalContext().getRequestParameterMap()" I \
> can't get the request parameters (submitted via commandlink/commandbutton parameter \
> or another parameter via hidden field f.e.)  If I added an actionlistener to the \
> commandlink (additionally) TWO requests were submitted:
> The first with all the correct params and the second without these
> params...
> I've tried the whole thing with client- and server-save-state: no
> differences.
> Looking in the internals of the requestParameterMap I saw that my wanted
> params are only request params but not portlet request params.
> This problem with the two requests were solved putting my backing-bean into the \
> session. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[prev in list] [next in list] [prev in thread] [next in thread]