You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Deepak Gothe (JIRA)" <de...@myfaces.apache.org> on 2010/03/02 12:23:27 UTC

[jira] Created: (PORTLETBRIDGE-126) Content before f:view should be not handled properly

Content before f:view should be not handled properly
----------------------------------------------------

                 Key: PORTLETBRIDGE-126
                 URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-126
             Project: MyFaces Portlet Bridge
          Issue Type: Bug
          Components: Impl
         Environment: Mojarra JSF Implementation
            Reporter: Deepak Gothe


In order to handle the content before f:view tag, the Mojarra JSF Implementation(starting 1.2_08), calls the method "flushContentToWrappedResponse" on the response. So in order for the bridge to handle this, the response wrapper should implement this method.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (PORTLETBRIDGE-126) Content before f:view should be handled properly

Posted by "Deepak Gothe (JIRA)" <de...@myfaces.apache.org>.
     [ https://issues.apache.org/jira/browse/PORTLETBRIDGE-126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Deepak Gothe updated PORTLETBRIDGE-126:
---------------------------------------

    Status: Patch Available  (was: Open)

> Content before f:view should be handled properly
> ------------------------------------------------
>
>                 Key: PORTLETBRIDGE-126
>                 URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-126
>             Project: MyFaces Portlet Bridge
>          Issue Type: Bug
>          Components: Impl
>    Affects Versions: 2.0.0-alpha
>         Environment: Mojarra JSF Implementation
>            Reporter: Deepak Gothe
>             Fix For: 2.0.0
>
>         Attachments: interweavingresponse.patch
>
>
> In order to handle the content before f:view tag, the Mojarra JSF Implementation(starting 1.2_08), calls the method "flushContentToWrappedResponse"  via reflection on the response. So in order for the bridge to handle this, the response wrapper should implement this method.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (PORTLETBRIDGE-126) Content before f:view should be handled properly

Posted by "Michael Freedman (JIRA)" <de...@myfaces.apache.org>.
     [ https://issues.apache.org/jira/browse/PORTLETBRIDGE-126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Freedman updated PORTLETBRIDGE-126:
-------------------------------------------

        Status: Resolved  (was: Patch Available)
      Assignee: Michael Freedman
    Resolution: Fixed

Spec/impl updated to support this.  By default the Bridge doesn't supply a responsewrapper (so it can properly work with a portlet 1.0 bridge write behind servlet filter).  However a user can configure the use of their own wrapper in a portlet init parameter.  A corresponding example has been provided to work with Mojarra (not possible with Myfaces -- still must use the serlvet filter).

> Content before f:view should be handled properly
> ------------------------------------------------
>
>                 Key: PORTLETBRIDGE-126
>                 URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-126
>             Project: MyFaces Portlet Bridge
>          Issue Type: Bug
>          Components: Impl
>    Affects Versions: 2.0.0-alpha
>         Environment: Mojarra JSF Implementation
>            Reporter: Deepak Gothe
>            Assignee: Michael Freedman
>             Fix For: 2.0.0
>
>         Attachments: interweavingresponse.patch
>
>
> In order to handle the content before f:view tag, the Mojarra JSF Implementation(starting 1.2_08), calls the method "flushContentToWrappedResponse"  via reflection on the response. So in order for the bridge to handle this, the response wrapper should implement this method.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.