[ http://issues.apache.org/jira/browse/PB-7?page=comments#action_12357818 ]
Michael Lipp commented on PB-7: ------------------------------- I have by now learned a lot about the requirements for a Portlet/JSF bridge by tracking down problems and patching the MyFaces bridge until it finally does now what I want. To summarize, (1) the bridge must carry over request attributes added during action handling to the rendering phase. The portal does not do this, it calls performAction with the ActionRequest and rendering with a RenderRequest and any attributes set on the ActionRequest are lost. JSF does not know about these different requests, it knows only of one request (context) used during the complete cycle. Thus, the bridge must make sure that it looks like this to JSF. (2) Request attributes set during performAction (i.e. carried over, see above) or during rendering a JSF-portlet must be removed from the request after rendering the JSF-portlet. This is necessary because only one request instance is used for rendering all portlets. (The portlet specification does not require the attributes of this request to be portlet scoped.) Therefore, if the JSF framework or application uses request attributes, there may be unintended interaction between the JSF applications. Neither the JSF framework nor the application is aware of a requirement to "scope" request attributes, because it does not "know" about the application being a portlet and several application being rendered with the same request (two or more JSF-portlets on one page). > Messages are not displayed, validation errors are ignored > --------------------------------------------------------- > > Key: PB-7 > URL: http://issues.apache.org/jira/browse/PB-7 > Project: Portals Bridges > Type: Bug > Components: jsf > Versions: 0.4 > Environment: Jetspeed2 > Reporter: Michael Lipp > Priority: Blocker > > If the JSF page produces messages (explicitly or implicitly due to validation > errors) these messages are not displayed. > Also (and probably related) validation errors are ignored, i.e. the model is > changed despite the error. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
