Set the session variable
Set the session variable
-- the value to set the session variable to
Perform an atomic update of this Settable.
Perform an atomic update of this Settable. The current value is passed to the function and the ValueHolder is set to the result of the function. This is enclosed in the performAtomicOperation method which will, by default, synchronize this instance
Different Vars require different mechanisms for synchronization.
Different Vars require different mechanisms for synchronization. This method implements the Var specific synchronization mechanism
Change the value of the Var for the lifespan of the function
Change the value of the Var for the lifespan of the function
Shadow of the 'is' method
Shadow of the 'is' method
The current value of the variable
The current value of the variable
This defines whether or not Lift will log when a RequestVar is set but then not read within the same request cycle.
This defines whether or not Lift will log when a RequestVar is set but then not read within the same request cycle. Change this to false to turn off logging. Logging can also be turned off globally via LiftRules.logUnreadRequestVars.
LiftRules#logUnreadRequestVars
Perform an atomic operation on the Settable.
Perform an atomic operation on the Settable. By default synchronizes the instance, but it could use other mechanisms
Shadow of the apply method
Shadow of the apply method
Set the Var if it has not been calculated
Set the Var if it has not been calculated
Has this Var been set or accessed and had its default value calculated
Has this Var been set or accessed and had its default value calculated
A non-side-effecting test if the value was initialized
A non-side-effecting test if the value was initialized
Applies the given function to the contents of this variable and sets the variable to the resulting value.
Applies the given function to the contents of this variable and sets the variable to the resulting value.
-- the function to apply and set the result from.
A typesafe container for data with a lifetime strictly equal to the processing of a single HTTP request. Unlike ordinary RequestVar instances, TransientRequestVars will not maintain data for servicing of AJAX callbacks from a rendered page. This is useful in cases where the value stored within the RequestVar cannot safely be used across multiple requests; an example of such a value is a JTA UserTransaction which has a lifecycle strictly coupled to the actul HTTP request handling by the enclosing container.