You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Thomas Andraschko (JIRA)" <de...@myfaces.apache.org> on 2017/02/09 19:25:41 UTC
[jira] [Resolved] (MYFACES-4075) SearchExpression API
[ https://issues.apache.org/jira/browse/MYFACES-4075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Andraschko resolved MYFACES-4075.
----------------------------------------
Resolution: Fixed
Fix Version/s: 2.3.0
> SearchExpression API
> --------------------
>
> Key: MYFACES-4075
> URL: https://issues.apache.org/jira/browse/MYFACES-4075
> Project: MyFaces Core
> Issue Type: New Feature
> Components: JSR-372
> Reporter: Leonardo Uribe
> Assignee: Leonardo Uribe
> Fix For: 2.3.0
>
>
> There is a proposal from PrimeFaces guys to include a search expression api to locate components in cases like f:ajax execute/render attributes, h:message for attribute and others.
> The idea comes from here:
> http://blog.primefaces.org/?p=2740
> The idea is support a syntax like this in the attributes:
> <clientId>
> :<id>
> <id>:<id>:<id>
> @<keyword>:<id>
> id:@<keyword>
> @<keyword>(<param1>)
> @<keyword>(<param1>,<param2>)
> There is a patch for this I have been working over the last weeks, but still require more tests and update the components in MyFaces Core 2.3 to use the new API.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)