commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 18068] - DefaultMapBag not Serializable
Date Mon, 21 Apr 2003 17:19:29 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18068>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18068

DefaultMapBag not Serializable





------- Additional Comments From rwaldhoff@apache.org  2003-04-21 17:19 -------
Maarten,

My concern isn't that the elements of the Bag aren't Serializable, but rather
that the Bag implementation itself may not be. I agree that no code change is
necessary  for most, perhaps all, subclasses of DefaultMapBag if one simply adds
"implements Serializable" to DefaultMapBag's declaration, but I cannot guarentee
that all instances of DefaultMapBag are indeed Serializable.  (In fact, right
now I can pretty much guarantee that no instances of DefaultMapBag are
serializable unless they've implemented their own writeObject/readObject
methods.)  Changing DefaultMapBag to implement Serializable has the opposite
effect, it requires that *all* instances of DefaultMapBag be serializable, or at
least implicitly declares them to be so--there's no "unimplements Serializable"
option.  

Is this unacceptable? Probably not. In fact it probably poses no problems in
practice.  One could do a lot worse than requiring all DefaultMapBag instances
to be Serializable.  It's just that I suspect one could do a lot better as well.
 At minimum, it's certainly not a fully backwards compatible change.

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message