Eh... probably.
--jason
On Aug 31, 2006, at 3:17 PM, Heinz Drews wrote:
I will create a jira.
Should there be a vote about the format of the uid?
--heinz
On 8/31/06, Jason Dillon <[EMAIL PROTECTED]> wrote:
On Aug 31, 2006, at 7:01 AM, Zakharov, Vasily M wrote:
> Note however, that small v
I will create a jira.
Should there be a vote about the format of the uid?
--heinz
On 8/31/06, Jason Dillon <[EMAIL PROTECTED]> wrote:
On Aug 31, 2006, at 7:01 AM, Zakharov, Vasily M wrote:
> Note however, that small values like 1 or 2 are traditionally used as
> serialVersionUIDs for synthetic
On Aug 31, 2006, at 7:01 AM, Zakharov, Vasily M wrote:
Note however, that small values like 1 or 2 are traditionally used as
serialVersionUIDs for synthetic and other system classes, like
Enums and
RMI Stubs, that are serialized in a special way. So using such
values in
"normal" classes may
On Aug 31, 2006, at 8:34 AM, Heinz Drews wrote:
Just as clarification, in the approach with the version number it was
not changed with each modification. Only if a change was causing an
impact to the serialized version.
I think that is the general point... only change the version when the
se
Vasily Zakharov
Intel Middleware Products Division
-Original Message-
From: Heinz Drews [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 31, 2006 9:46 AM
To: geronimo-dev
Subject: Standard for serialVersionUID
As I have mentioned in another message I have accidently used class
files in
leware Products Division
-Original Message-
From: Heinz Drews [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 31, 2006 9:46 AM
To: geronimo-dev
Subject: Standard for serialVersionUID
As I have mentioned in another message I have accidently used class
files in modules created by Ec
As I have mentioned in another message I have accidently used class
files in modules created by Eclipse embeded compiler. This calculates
serialVersionUID different way then javac.
I think that adding serialVersionUID to all serializable class would
address the situation best.
There are quite a
