-
Type:
New Feature
-
Status: Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: liferay-faces-2.1.2-ga3, liferay-faces-3.0.2-legacy-ga3, liferay-faces-3.1.2-ga3
-
Component/s: Liferay Faces Util
-
Labels:None
JSP has a feature in which custom tags can be developed for use in .jsp files.
For example, Liferay Portal provides the html-top JSP tag so that the JSP developer can specify CSS or JavaScript resources that appear in the <head>...</head> section of the rendered portal page:
<liferay-util:html-top />
In the case of the html-top tag, the underlying com.liferay.taglib.util.HtmlTopTag is invoked, which works with the underlying PageContext and JspWriter.
When developing JSF applications with the Facelet View Declaration Language, it is not possible to utilize JSP tags. In order to provide corresponding Facelet tags and re-use code as much as possible, it is necessary to provide the ability to invoke JSP Tag classes directly (outside of JSP technology) so that the resulting markup can be captured to a String. The corresponding JSF component renderers can then parse the string result and optionally write the markup to the response.
- relates
-
FACES-1698 Implement methods inside of PageContextAdapter rather than throwing UnsupportedOperationException
-
- Closed
-