You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by bu...@apache.org on 2005/05/25 20:26:48 UTC
DO NOT REPLY [Bug 35068] New: -
[shale] Position (inner class) should implement Serializable
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=35068>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=35068
Summary: [shale] Position (inner class) should implement
Serializable
Product: Struts
Version: Nightly Build
Platform: PC
OS/Version: other
Status: NEW
Severity: normal
Priority: P2
Component: Shale
AssignedTo: dev@struts.apache.org
ReportedBy: sean.schofield@gmail.com
At one point Tomcat complained about not being able to serialize
Status$Position. This class should really implement Serializable otherwise any
class that implements Status and makes use of Position (such as Status) cannot
be serialized.
Also, this got me thinking about why Position is declared as part of the Status
interface. Presumably there is a good reason but I can't think of any
advantages to this offhand. In fact its a little bit disconcerting for the
average user (me) who has not ever seen an inner class in an interface before.
Obviously its permissable but I think we should consider making it its own class
unless there is a compelling reason to have it this way.
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org