-
Type:
Bug
-
Status: Closed
-
Resolution: Won't Fix
-
Affects Version/s: 7.0.0 CE GA1
-
Fix Version/s: None
-
Labels:None
-
Fix Priority:3
{markdown}
Steps to reproduce:
1. Add `module.framework.web.generator.generated.wabs.store=true` to your `portlet-ext.properties` file:
echo module.framework.web.generator.generated.wabs.store=true >> portlet-ext.properties
2. Start Liferay Portal.
3. Deploy the attached portlet to Liferay Portal:
cp ~/Downloads/com.liferay.faces.demo.jsf.ds.applicant.portlet.war $LIFERAY_HOME/deploy/
4. Extract the generated servlet declaration from the `web.xml` of the deployed wab:
unzipp osgi/wabs/com.liferay.faces.demo.jsf.ds.applicant.portlet*.war WEB-INF/web.xml |\
grep -B 1 -A 7 '<servlet'
If the bug still exists, the portlet servlet declaration and servlet-mapping will not be generated.
The generated servlet and mapping should probably look something like this:{markdown}
Steps to reproduce:
1. Add `module.framework.web.generator.generated.wabs.store=true` to your `portlet-ext.properties` file:
echo module.framework.web.generator.generated.wabs.store=true >> portlet-ext.properties
2. Start Liferay Portal.
3. Deploy the attached portlet to Liferay Portal:
cp ~/Downloads/com.liferay.faces.demo.jsf.ds.applicant.portlet.war $LIFERAY_HOME/deploy/
4. Extract the generated servlet declaration from the `web.xml` of the deployed wab:
unzip
grep -B 1 -A 7 '<servlet'
If the bug still exists, the portlet servlet declaration and servlet-mapping will not be generated.
The generated servlet and mapping should probably look something like this:{markdown}
<servlet> <servlet-name>Portlet Servlet</servlet-name> <servlet-class>com.liferay.portal.kernel.servlet.PortletServlet</servlet-class> <init-param> <param-name>portlet-class</param-name> <param-value>my.portlet.PortletClass</param-value> </init-param> <load-on-startup>1</load-on-startup> </servlet> <!-- ... --> <servlet-mapping> <servlet-name>Portlet Servlet</servlet-name> <url-pattern>/portlet-servlet/*</url-pattern> </servlet-mapping>
Note: In order to test the fix for this issue, you may need to add the workaround for LPS-66225 if that issue has not been fixed yet. If you don't apply that workaround and LPS-66225 has not been fixed yet, you will be unable to test that the portlet is functioning.