You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Martin Marinschek (JIRA)" <de...@myfaces.apache.org> on 2006/09/20 22:51:23 UTC
[jira] Commented: (MYFACES-1197) Docs for ifMessage component
[ http://issues.apache.org/jira/browse/MYFACES-1197?page=comments#action_12436340 ]
Martin Marinschek commented on MYFACES-1197:
--------------------------------------------
After some time has passed by, I'm thinking differently about this one as well.
This is my current take at this problem:
1) go with Adam's suggestion of using a custom VariableResolver which adds a new implicit object (let's call it myfacesContext), add an attribute storedComponentClientId to this implicit object.
2) create a new component which does nothing but setting the parent-client-id into this myfacesContext, e.g.: <t:storeParentComponentClientId param="#{myfacesContext.storedComponentClientId}"/>
where param is optional (by default, it's set to where the example points, you can change this to somewhere else if need be).
3) now you can use this stored-client-id in your el-expressions, and do a lot more than what ifMessage would provide.
regards,
Martin
> Docs for ifMessage component
> ----------------------------
>
> Key: MYFACES-1197
> URL: http://issues.apache.org/jira/browse/MYFACES-1197
> Project: MyFaces Core
> Issue Type: Improvement
> Components: General
> Affects Versions: 1.1.2-SNAPSHOT
> Reporter: Mike Youngstrom
> Attachments: ifMessageDocs.patch
>
>
> Here is a patch with docs for the ifMessage component I donated.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira