store-properties
Specifies session persistence (storage) properties.
Superelements
session-manager (sun-web.xml)
Subelements
The following table describes subelements for the store-properties element.
store-properties Subelements
|
|
|
|
zero or more |
Specifies a
property, which has a name and a value. |
|
Properties
The following table describes properties for the store-properties element.
store-properties Properties
|
|
|
|
domain-dir/generated/jsp/app-name/module-name_war |
Specifies the absolute or
relative pathname of the directory into which individual session files are written. A
relative path is relative to the temporary work directory for this web module. Applicable
only if the persistence-type attribute of the parent session-manager element is file. |
|
session |
Specifies how
much of the session state is stored. Allowed values are as follows:
session - The entire session state is stored every time. This mode provides the best guarantee that your session data is correctly stored for any distributable web module.
modified-session - The entire session state is stored if it has been modified. A session is considered to have been modified if HttpSession.setAttribute() or HttpSession.removeAttribute() was called. You must guarantee that setAttribute() is called every time an attribute is changed. This is not a Java EE specification requirement, but it is required for this mode to work properly.
modified-attribute - Only modified session attributes are stored. For this mode to work properly, you must follow some guidelines, which are explained immediately following this table.
Applicable only
if the persistence-type attribute of the parent session-manager element is replicated.
Note - The replicated persistence type
is not supported in GlassFish v3.
|
|
If the persistenceScope store property is set to modified-attribute, a web module
must follow these guidelines:
-
Call setAttribute() every time the session state is modified.
-
Make sure there are no cross-references between attributes. The object graph under each distinct attribute key is serialized and stored separately. If there are any object cross references between the objects under each separate key, they are not serialized and deserialized correctly.
-
Distribute the session state across multiple attributes, or at least between a read-only attribute and a modifiable attribute.