[ 
https://issues.apache.org/jira/browse/PORTLETBRIDGE-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12597170#action_12597170
 ] 

Michael Freedman commented on PORTLETBRIDGE-34:
-----------------------------------------------

This isn't exactly what I had in mind:
    1) I prefer to not use instanceof to determine if we are running in myFaces
    2) I prefer to determine the marker that should be used by actually finding 
the marker in the response.   I.e. if we don't know the market from a previous 
render we search the response first for the marker identified by the init param 
-- if not the right one then the RIs market -- and still if noit the right one, 
the MyFaces marker.

As for where to put the constant -- it belongs in 
javax.portlet.faces.Bridge.java

Can you make these modifications or If you would prefer, I can do this next 
week when I return from my business trip?

> 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, 
> patchPortletBridgeMyfacesVer2.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.

Reply via email to