cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Markus Wolf (JIRA)" <j...@apache.org>
Subject [jira] Commented: (COCOON-2049) Faces Block and responseComplete handling
Date Thu, 19 Apr 2007 14:28:15 GMT

    [ https://issues.apache.org/jira/browse/COCOON-2049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12490077
] 

Markus Wolf commented on COCOON-2049:
-------------------------------------

One possible patch would be to have the FacesAction implement AbstractReader and just set
the content-type from the response.
So nothing is added to the response and the cocoon pipeline ends.
It's a kind of hack, since cocoon actions are not readers but it does work.

> Faces Block and responseComplete handling
> -----------------------------------------
>
>                 Key: COCOON-2049
>                 URL: https://issues.apache.org/jira/browse/COCOON-2049
>             Project: Cocoon
>          Issue Type: Bug
>          Components: Blocks: (Undefined)
>    Affects Versions: 2.1.10
>            Reporter: Markus Wolf
>
> The faces block does not handle a responseComplete FacesContext correct.
> When a faces backing bean calls responseComplete, then no additional response has to
be rendered (this is from the spec).
> But in cocoon when a response is completed from a backing bean the redirect to a view
from the RedirectImpl in the FacesAction is not executed, because the LifecycleImpl from MyFaces
does not call a dispatch. Therefore cocoon executes additional actions from the sitemap (the
one after the <map:act />).

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


Mime
View raw message