[
https://issues.apache.org/jira/browse/PB-92?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Trevor Lohrbeer updated PB-92:
------------------------------
Attachment: servlet-and-portlets-side-by-side-v2.patch
Attached is an updated patch. My isPortlet() function in PortletViewHandlerImpl
was not working correctly because PortletExternalContextImpl does not implement
javax.portlet.PortletContext. Instead, now I'm testing to see if the
facesContext is an instance of PortletFacesContextImpl, which should work as
long as the FacesContextFactory remains the portals bridges
FacesContextFactoryImpl.
> JSF servlets don't work when used side-by-side with JSF portlets
> ----------------------------------------------------------------
>
> Key: PB-92
> URL: https://issues.apache.org/jira/browse/PB-92
> Project: Portals Bridges
> Issue Type: Bug
> Components: jsf
> Affects Versions: 1.0.4
> Environment: JBoss 4.0.5 running Apache MyFaces 1.1.5,
> portlet-bridges 1.0.4
> Reporter: Trevor Lohrbeer
> Attachments: servlet-and-portlets-side-by-side-v2.patch,
> servlet-and-portlets-side-by-side.patch
>
>
> When the portlet bridges library is included in a WAR file, JSP pages can
> only be accessed through portlets, not directly from the FacesServlet.
> Attempting to access a JSP page through the FacesServlet results in an
> IllegalArgumentException with the message "Only PortletContext supported".
> The stack trace shows that this occurs when attempting to access the session
> map.
> Upon further investigation, the problem stems from the fact that the
> portlet-bridges-jsf library includes a META-INF/faces-config.xml file which
> installs a custom FacesContextFactory and ViewHandler. These are installed
> for the entire web application, yet are designed only to work with portlets.
> Thus, running JSF portlets and servlets side-by-side results in errors.
--
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: [email protected]
For additional commands, e-mail: [email protected]
