[
https://issues.apache.org/jira/browse/TOMAHAWK-1215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12583297#action_12583297
]
Mario Ivankovits commented on TOMAHAWK-1215:
--------------------------------------------
Why do you transfer the message and not simply the output of the messages
component(s)?
The problem I see with the current solution is that it do not honor any applied
stylesheet/class configuration or a custom messages renderer. Instead you
"render" on client-side - which seems too limiting to me.
I see the use case of this solution when I think about the "queueing" stuff we
talked about, but for the common use case of PPR (simple form transmissal) you
do not need the messages "machine readable".
At least having an attribute "messages="id,id,id" which simply transfers the
server side rendered output of those components would be great.
Instead of naming it messages="" you could also name it more general
externalComponents="" (or something like that) - Then it will be possible to
configure components outside of the current pprPanelGroup - most likely the
messages component.
> Add a communication channel for FacesMessages to the PPRPanelGroup
> ------------------------------------------------------------------
>
> Key: TOMAHAWK-1215
> URL: https://issues.apache.org/jira/browse/TOMAHAWK-1215
> Project: MyFaces Tomahawk
> Issue Type: New Feature
> Components: PPRPanelGroup
> Reporter: Ernst Fastl
> Assignee: Ernst Fastl
> Fix For: 1.1.7-SNAPSHOT
>
>
> As any conventional JSF request PPR requests can lead to conversion and
> validation errors or other
> events which produce FacesMessages. The PPRPanelGroup should be enhanced to
> transport
> these messages in a separate channel (meaning a different type of child
> element in the xml-response).
> Optionally a messages-component could be build to which these messages can
> subsequently be added.
> Since this component might collect a lot of messages over various PPR
> requests it could have
> a clear button or something similar which enables the user to clear the
> messages
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
