myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Blake Sullivan (JIRA)" <>
Subject [jira] Created: (TRINIDAD-1249) Further improvements to JIRA-1245 High Availability Testing and Support
Date Mon, 06 Oct 2008 07:11:44 GMT
Further improvements to JIRA-1245  High Availability Testing and Support

                 Key: TRINIDAD-1249
             Project: MyFaces Trinidad
          Issue Type: Improvement
         Environment: all
            Reporter: Blake Sullivan

1) Add support for checking the Application Map, similar to the Session Map checking in JIRA-1245
by adding "application" as one of the values allowed in the system property. 
The value can be retrieved programmatically by calling StateUtils:
  public static boolean checkApplicationSerialization(ExternalContext extContext)

2) Increase the robustness of Serializability testing for Application and Session Maps by
not simply testing that the keys and values passed to the Maps implement Serializable, but
by actually attempting to Serialize the keys and values.  This catches cases where the Object
implements Serializable but itself contains unSerializable objects--for example a HashMap.

This service is available through the CollectionUtils function:
  public static <K,V> Map<K, V> getCheckedSerializationMap(Map<K, V> map)

3) Add a TransientHolder class for Objects that are required to be Serializable (for example,
they need to be added to the Session Map on a Servlet Engine configured for High Availability),
but, in fact, should not be Serialized.

4) Fix the ChangeManager intialization in the RequestContext to ensure that it is added to
the Application Map using a TransientHolder if the ChangeManager implementation is not Serializable.


This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message