[
https://issues.apache.org/jira/browse/TRINIDAD-2284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13440231#comment-13440231
]
Thomas Möller commented on TRINIDAD-2284:
-----------------------------------------
I provided a patch that implements the behaviour that I found here:
http://javaserverfaces.java.net/nonav/docs/2.0/pdldocs/facelets/h/form.html. In
my scenario (liferay 6.1.1, mojarra 2.1.3-b02, bridge 3.1.0-rc2) PPRs work now.
Attention: in my test I had to 1) include the mojarra.js myself via
<h:outputScript name="jsf.js" library="javax.faces" target="head" /> and 2)
define an id for the PPR-triggering component.
> Trinidad CoreForm does not render standard javax.faces.encodedURL hidden field
> ------------------------------------------------------------------------------
>
> Key: TRINIDAD-2284
> URL: https://issues.apache.org/jira/browse/TRINIDAD-2284
> Project: MyFaces Trinidad
> Issue Type: Bug
> Components: Components
> Affects Versions: 2.0.1-core
> Reporter: Neil Griffin
> Attachments: patch.zip
>
>
> Trinidad PPR Ajax does not work in JSF 2 portlet bridges (like Liferay Faces
> Bridge) because the renderer for tr:form does not render the standard hidden
> field:
> <input type="hidden" name="javax.faces.encodedURL" value="..." />
> http://docs.oracle.com/javaee/6/javaserverfaces/2.1/docs/renderkitdocs/HTML_BASIC/javax.faces.Formjavax.faces.Form.html
> Since the field is not rendered, jsf.js uses the "action" attribute of the
> form, which invokes the ACTION_PHASE of the portlet lifecycle. If the hidden
> field is rendered properly, then the value of the hidden field is a portlet
> ResourceURL which invokes the RESOURCE_PHASE of the portlet lifecycle.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
