[
https://issues.apache.org/jira/browse/PORTLETBRIDGE-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12596821#action_12596821
]
Scott O'Bryan commented on PORTLETBRIDGE-34:
--------------------------------------------
Yeah, I think I like this better. Mike is also going to file an issue with the
JSF2.0 folks so that this value may either be standardized or exposed though a
constant. For now though, Mike's suggestion covers the two major JSF
implementations and allows for others to be plugged in.
What do you think Leonardo, is it doable?
> Bridge does not work with Myfaces with state saving = client
> ------------------------------------------------------------
>
> Key: PORTLETBRIDGE-34
> URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-34
> Project: MyFaces Portlet Bridge
> Issue Type: Bug
> Affects Versions: 1.0.0-alpha-2
> Environment: windows xp, tomcat 6.0.16 and jetty, pluto
> Reporter: Leonardo Uribe
> Attachments: patchPortletBridgeMyfaces.patch
>
>
> The javax.faces.ViewState hidden field is not rendered!
> The problem is on PortletViewHandlerImpl.java. The field:
> private static final String SAVESTATE_FIELD_MARKER =
> "~com.sun.faces.saveStateFieldMarker~";
> Is the problem. If ri is present this is the value, if not myfaces state
> field marker should be used
> I will attach a patch (the easiest solution that I could find), and if no
> objections, I'll commit it.
> Reproduce the error is simple. Just use archetype for portlets and change the
> param
> javax.faces.STATE_SAVING_METHOD
> to client
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
