[OmniFaces utilities] The
Callback
represents a collection of un-serializable callback interfaces. Useful in (mini) visitor and strategy patterns.
In case you don't know, OmniFaces 2.0 comes with a set of un-serializable callback interfaces useful in (mini) visitor and strategy patterns. These interfaces are available in the final class org.omnifaces.util.Callback.
Starting with OmniFaces 2.1 the callback which takes two arguments was removed. For the rest of Callbacks listed below, OmniFaces 2.1 provides a Serializable version.
Let's see what we have in OmniFaces 2.0:
Starting with OmniFaces 2.1 the callback which takes two arguments was removed. For the rest of Callbacks listed below, OmniFaces 2.1 provides a Serializable version.
Let's see what we have in OmniFaces 2.0:
·
void callback
Check out the blog Callback submenu to see several examples of using these interfaces to:
- subscribe the given callback instance to the given component that get invoked only in the current request when the given component system event type is published on the given component (only in OmniFaces 2.1)
- unsubscribe the given event listener on the given event from the given component (only in OmniFaces 2.1)
- OmniFaces 2.0 - ReadOnlyValueExpression that can be set when the "real" value is not yet available
- OmniFaces 2.1 - ReadOnlyValueExpression that can be set when the "real" value is not yet available (only in OmniFaces 2.1)
Niciun comentariu :
Trimiteți un comentariu