Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 3.3
-
Fix Version/s: EE-3.3.0.GA, 4.0.BETA, 4.0
-
Component/s: Sample Apps
-
Labels:None
-
Environment:Portal portlet LiferayFaces Bridge
-
Workaround Exists:Yes
-
Workaround Description:Manually remove the listeners if you are deploying the example in an environment that does not include the LiferayFaces Bridge.
Description
As part of a fix for ICE-9156, we modified the chat and showcase portlet examples to include listeners in the web.xml. This was done as per the recommendations outlined in http://issues.liferay.com/browse/FACES-1511:
{code}<!-- Specifying these listeners in this order as per http://issues.liferay.com/browse/FACES-1511 -->
<listener>
<listener-class>com.sun.faces.config.ConfigureListener</listener-class>
</listener>
<listener>
<listener-class>com.liferay.faces.bridge.servlet.BridgeSessionListener</listener-class>
</listener>{code}
The problem is that if a web.xml contains these listener declarations and the LiferayFaces Bridge is not present, the deployment will fail with errors about not being able to find the class. This can happen if the chat application is deployed directly to Tomcat or the Showcase Portlet application is deployed to Liferay but using the older PortletFaces Bridge.
We should create separate web.xml files for the chat and chat-portlet examples to help isolate the issue to portlet deployments only.
{code}<!-- Specifying these listeners in this order as per http://issues.liferay.com/browse/FACES-1511 -->
<listener>
<listener-class>com.sun.faces.config.ConfigureListener</listener-class>
</listener>
<listener>
<listener-class>com.liferay.faces.bridge.servlet.BridgeSessionListener</listener-class>
</listener>{code}
The problem is that if a web.xml contains these listener declarations and the LiferayFaces Bridge is not present, the deployment will fail with errors about not being able to find the class. This can happen if the chat application is deployed directly to Tomcat or the Showcase Portlet application is deployed to Liferay but using the older PortletFaces Bridge.
We should create separate web.xml files for the chat and chat-portlet examples to help isolate the issue to portlet deployments only.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
I've added a separate web.xml to the chat-portlet example that includes the listeners and removed them from the web.xml of the non-portlet application. This should fix the problem of being able to deploy chat in a non-portlet environment. There will still be problems if the PortletFaces Bridge is used but we are working to move away from it altogether at some point.