portals-bridges-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Marinschek (JIRA)" <bridges-...@portals.apache.org>
Subject [jira] Commented: (PB-73) Cumulative patch for better storing the ViewRoot, disabling calling restoreState on the ViewRoot, and better SessionMap/RequestParameterMap/ApplicationMap handling in the servlet case
Date Sat, 01 Sep 2007 09:09:18 GMT

    [ https://issues.apache.org/jira/browse/PB-73?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12524263
] 

Martin Marinschek commented on PB-73:
-------------------------------------

Two more things:

1) the pom.xml also includes the sources of the jsf-portlet-bridge in the distribution with
this version and sets two dependencies (JSP-API and JSF-API to provided)

2) the portlet underlying this bridge is being passed on as a request-parameter, so that afterwards
the portlet-name can be retrieved. Eventually, there might be a better solution for this,
but we didn't find one. 

regards,

Martin

> Cumulative patch for better storing the ViewRoot, disabling calling restoreState on the
ViewRoot, and better SessionMap/RequestParameterMap/ApplicationMap handling in the servlet
case
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: PB-73
>                 URL: https://issues.apache.org/jira/browse/PB-73
>             Project: Portals Bridges
>          Issue Type: Bug
>          Components: jsf
>    Affects Versions: 1.0
>            Reporter: Martin Marinschek
>         Attachments: jsf-portlet-bridge.patch
>
>
> This patch tries to resolve three issues with the current bridge. It has been created
by Thomas Spiegl, Bernhard Huemer and me (just to do the honours ;).
> 1) The UIViewRoot is directly put into the session - this doesn't fly if load-balancing
is switched on and the session is serialized between servers, as no JSF-component is serializable
(instead, it implements state-holder, and one has to call the appropriate methods restoreState/saveState,
and additionally save the tree-structure.
> 2) In the FacesPortlet, a superfluous call to restoreState is happening - if the UIViewRoot
is properly restored, restoreState should not be called anymore
> 3) the SessionMap/RequestParameterMap etc. will only work if behind a portlet. In some
cases, the JSF-app might run both behind a portlet and a servlet
> regards,
> Martin

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


---------------------------------------------------------------------
To unsubscribe, e-mail: bridges-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: bridges-dev-help@portals.apache.org


Mime
View raw message