Details
-
Bug
-
Status: Ready for Testing
-
Resolution: Fixed
-
7.4.0 CE GA1
-
7.3.x, 7.2.x, 7.1.x, 7.0.x
-
Committed
-
1
Description
Problem Background
The JspAnalyzerPlugin is able to determine taglib usage for scriptlet syntax, e.g.:
<%@ taglib uri="http://java.sun.com/jsp/jstl/core" prefix="c" %> <%@ taglib uri="http://liferay.com/tld/clay" prefix="clay" %><%@ taglib uri="http://liferay.com/tld/ui" prefix="liferay-ui" %> <%@ taglib uri="http://java.sun.com/portlet_3_0" prefix="portlet" %>
However, it is not able to determine taglib usage for JSPX syntax, e.g.:
<?xml version="1.0" encoding="UTF-8"?> <jsp:root xmlns:c="http://java.sun.com/jsp/jstl/core" xmlns:clay="http://liferay.com/tld/clay" xmlns:liferay-ui="http://liferay.com/tld/ui" xmlns:portlet="http://xmlns.jcp.org/portlet_3_0" version="2.1"> ... </jsp:root>
Because of this, it is necessary to manually add Require-Capability syntax to liferay-plugin-package.properties (for WAR artifacts), e.g.:
Require-Capability: osgi.extender; filter:="(&(osgi.extender=jsp.taglib)(uri=http://liferay.com/tld/clay))",osgi.extender;"
Steps to Reproduce
1. Extract the attached lps133987-src.zip artifact to Liferay Workspace
2. Build the module with gradlew clean deploy
3. Extract the resulting JAR module and examine the META-INF/MANIFEST.MF file
Expected Results
The Require-Capability section of the MANIFEST.MF file contains the following filter:
filter:="(&(osgi.extender=jsp.taglib)(uri=http://xmlns.jcp.org/portlet_3_0))"
Actual Results
The filter is not found in the MANIFEST.MF file.
Attachments
Issue Links
- fixes
-
FACES-3616 Portlet com.liferay.faces.demo.jsf.jsp.applicant failed to start
-
- Closed
-