[ http://issues.apache.org/struts/browse/SHALE-63?page=all ]
Craig McClanahan moved STR-2667 to SHALE-63:
--------------------------------------------
Project: Shale (was: Struts Action 1)
Key: SHALE-63 (was: STR-2667)
Component: (was: Shale)
Version: (was: Nightly Build)
Assign To: (was: Struts Developer Mailing List)
> [shale] Implement serializability on classes potentially stored in session
> scope
> --------------------------------------------------------------------------------
>
> Key: SHALE-63
> URL: http://issues.apache.org/struts/browse/SHALE-63
> Project: Shale
> Type: Bug
> Environment: Operating System: other
> Platform: Other
> Reporter: Craig McClanahan
>
> The following Shale implementation classes can potentially be stored in
> session
> scope (and therefore be required by the J2EE spec to be serializable), but are
> not currently serializable:
> * org.apache.shale.validator.CommonsValidator
> * org.apache.shale.dialog.impl.DialogImpl
> Unit tests also need to be added to verify the serializability of these and
> other classes that must implement it.
> The following classes inherit "implements Serializable" from their parent
> class
> in Commons Chain, even though they are not and cannot actually implement
> this.
> That is not a direct problem for Shale usage (these classes are only used to
> represent per-request state information), but might still get flagged on
> audits
> of a Shale based webapp:
> * org.apache.shale.faces.ShaleWebContext
> * org.apache.shale.remote.RemoteContext
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/struts/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
