repo1.maven.org$maven2@org.apache.wicket$wicket@1.3.3
repo1.maven.org$maven2@org.apache.wicket$wicket@1.3.3@org$apache$wicket$model$IModel.java
file
oh
o
[]
package org.apache.wicket.model;
A IModel wraps the actual model Object used by a Component. IModel implementations are used as a
facade for the real model so that users have control over the actual persistence strategy. Note
that objects implementing this interface will be stored in the Session. Hence, you should use
(non-transient) instance variables sparingly.
- Basic Models - To implement a basic (non-detachable) model which holds its entire
state in the Session, you can use the simple model wrapper
Model.
- Detachable Models - IModel inherits a hook,
IDetachable.detach(), so that
interface implementers can detach transient information when a model is no longer being actively
used by the framework. This reduces memory use and reduces the expense of replicating the model
in a clustered server environment. To implement a detachable model, you should generally extend
LoadableDetachableModel instead of implementing IModel directly.
- Property Models - The AbstractPropertyModel class provides default functionality for
property models. A property model provides access to a particular property of its wrapped model.
- Compound Property Models - The IModel interface is parameterized by Component,
allowing a model to be shared among several Components. When the
getObject()method
is called, the value returned will depend on the Component which is asking for the value.
Likewise, the setObject(java.lang.Object)method sets a different property depending on
which Component is doing the setting. For more information on CompoundPropertyModels and model
inheritance, see CompoundPropertyModeland
org.apache.wicket.Page.
Sets the model object.
- Parameters:
object
The model object