[
https://issues.apache.org/jira/browse/PORTLETBRIDGE-143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Freedman resolved PORTLETBRIDGE-143.
--------------------------------------------
Fix Version/s: 1.0.0
2.0.0
Resolution: Fixed
A bunch of fixes: the example were updated to set the wrapped response they
create/use on the external context as this is what is referenced when checking
to see if the specific writebehind api is implemented.
Also changed the bridge's externalContext so a servletResponse can be set on
setResponse.
Finally -- removed use of bridge response wrappers and added a portlet init
parameter that allows a developer to configure a response wrapper they want
used when the render is dispatched -- i.e. if someone wants to provide the
write behind behavior in a response wrapper (currently can only be done for
Mojarra) they can write the wrapper and configure the bridge to use. An
example has been added that demonstrates this.
> WriteBehindResponse mechanism(s) not working properly
> -----------------------------------------------------
>
> Key: PORTLETBRIDGE-143
> URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-143
> Project: MyFaces Portlet Bridge
> Issue Type: Bug
> Affects Versions: 1.0.0-beta, 2.0.0-alpha
> Reporter: Michael Freedman
> Assignee: Michael Freedman
> Fix For: 1.0.0, 2.0.0
>
>
> Multiple problems: in portlet 2.0 the wrapper used by the bridge conflicts
> with the servlet filter mechanism. In addition the examples that demonstrate
> how to write MyFaces and Mojarra filters don't work properly because they
> haven't set their wrapped responses as the ExternalContext response but the
> ViewTag impls for instanceof against the ExternalContext response.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
