- <h:body>
- <h:outputLabel id="label" for="@next" value="Test" />
- <h:inputText id="input">
- <f:ajax render="@this @next" />
- </h:inputText>
- <h:inputText id="input2" />
- </h:body>
APIs for searching for components in the component tree by using expressions.
See: Description
Interface | Description |
---|---|
UntargetableComponent |
Components implementing this interface are ignored by the algorithm -
especially in the implementation of
@child(n) , @next and @previous . |
Class | Description |
---|---|
SearchExpressionContext |
A context object that is used to hold state relating to resolve a search expression. |
SearchExpressionContextFactory |
Provide for separation of interface and
implementation for the |
SearchExpressionHandler |
The SearchExpressionHandler is responsible for
resolving search expression(s)
|
SearchExpressionHandlerWrapper |
Provides a simple implementation of |
SearchKeywordContext |
SearchKeywordContext
provides context information that may be useful to
|
SearchKeywordResolver |
A SearchKeywordResolver is responsible for resolving a single keyword. |
Enum | Description |
---|---|
SearchExpressionHint |
An enum that specifies hints that impact the behavior of a component tree search. |
Exception | Description |
---|---|
ComponentNotFoundException |
Typed |
APIs for searching for components in the component tree by using expressions.
This feature has two entry points: for the page author and for the Java programmer. Following is a brief overview of each.
The following tags support the use of search
expressions: <h:message />
, <h:messages
/>
, <h:outputLabel />
,
and <f:ajax />
. Each of those tags have one or
more attributes whose value must be a client identifier. This feature
expands the capability of those attributes to be search expressions.
A search expression is space separated list of tokens, where a token
can either be a client identifier, a search keyword, or a combination
of both. See the specification
for SearchKeywordResolver
for the list of keywords that must be supported. See the
specification
for SearchExpressionHandler
to learn how the search is performed.
Here is a brief example of the page author use case:
Using search expressions from Java code offers more flexibility.
One must obtain a handle to
the SearchExpressionHandler
and invoke methods on it as desired.
The following example resolves to a clientId:
The following example resolves to a component:
The following example uses multiple expressions and therefor resolves to multiple components:
Creation of the SearchExpressionContext
As with other factories in JSF, the FactoryFinder
is
used by the system to create instances of
the SearchExpressionContext
which holds state during the
operation of this API.
Adding new SearchKewordResolver
s
See SearchKeywordResolver
for the specification of how the set of keywords can be expanded.
Copyright © 1996-2017, Oracle and/or its affiliates. All Rights Reserved. Use is subject to license terms.