David Sean Taylor <david <at> bluesunrise.com> writes: > Yes, of course I know about those. > But now I have forgotten what exactly your problem was. > Thought you were having problems with JSF portlets from a 3rd party... >
I think there are basically two problems with JSF apps in the portal: 1. This one is limited to the JSF bridge. Basically, an application which uses the JSF bridge cannot be used outside of jetspeed (ie have its URIs invoked directly). You get this error: javax.faces.FacesException: Unsupported context type org.apache.catalina.core.ApplicationContextFacade org.apache.portals.bridges.jsf.FacesContextFactoryImpl .getFacesContext(FacesContextFactoryImpl.java:58) javax.faces.webapp.FacesServlet.service(FacesServlet.java:102) org.apache.myfaces.component.html.util.ExtensionsFilter .doFilter(ExtensionsFilter.java:119) 2. The second problem seems to be with JSF apps used in the portal in general. At least it manifests itself with both the myfaces portlet implementation and the jsf-app that uses the bridge. Basically, I have a managed bean in the request scope and a html form that references it and posts to an action. I have a navigation rule sending the user back to the html form. Since I am not using the redirect option in my navigation rule, the form values should show up in the html (since a forward was done). This is not happening, the form/bean data is lost. If I use the app outside of jetspeed, then the data is *not* lost. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
