|
[
Permlink
| « Hide
]
Henning Schmiedehausen added a comment - 06/Aug/07 02:17 PM
Also contains serializable patch, apply with care.
I agree with the hasArg change. My preference for serializable classes is to use the number which would be generated by serialver. This way, if someone is already serializing this class, it won't break their code if they don't upgrade both the client and server at the same time.
Other people prefer to start a 1L and increment each time the public interface changes. I don't know if Apache has a standard one way or the other. You can not serialize the class currently. It is not serializable.
It has no version, because it needs no version. I don't know anything about a serialization standard @ Apache, but I consider 1L and incrementing to be more readable. I don't really care about the version, as long as the classes become serializable. I have some time this weekend, so I could apply the patches, unless someone objects strongly. Patch is wonky btw - it fails to apply against the branch, and when I look at it by hand, you've missed one of the hasArg usages.
Cleaned up the patch a little bit. It applies to the 1.x branch for me without any problems.
The hasArg instance that Henri thought Henning missed is not an issue – it's just a local variable. +1 to adopting this. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||