[ http://issues.apache.org/jira/browse/PB-7?page=comments#action_12357862 ]
Michael Lipp commented on PB-7: ------------------------------- This does not solve the issue with request attributes. The FacesContext uses the ExternalContext from the current request to access request attributes and therefore the request attributes are not carried over by simply saving the FacesContext :-( Note that part of the portlet support of MyFaces has been coded in MyFaces. The MyFaces portlet bridge sets a special flag to indicate the portlet context (only found this after looking very close). Of course, the generic bridge from this (PB) project cannot do this (or only after making sure that the JSF implementation used in the current request is MyFaces). IMHO, this project will not be able to deliver a generic JSF/portlet bridge without talking to the MyFaces project (and maybe others)! > 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]
