Mailing-List: contact dev-help@cayenne.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cayenne.apache.org
Received-SPF: pass (nike.apache.org: domain of mkienenb@gmail.com designates
 74.125.82.171 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAA-upzoaWC38DJKVp0bCzKWEk=FmLC+0i1fByX4rk7GbVNEm8w@mail.gmail.com>
References: 
 <CAA-upzoaWC38DJKVp0bCzKWEk=FmLC+0i1fByX4rk7GbVNEm8w@mail.gmail.com>
From: Mike Kienenberger <mkienenb@gmail.com>
Date: Thu, 14 Jun 2012 10:14:38 -0400
Message-ID: 
 <CAM1yOjYWYG3Z67c2Q-7shRF3BKmx1E4251xgQ3OTVgEmZ2mRsg@mail.gmail.com>
Subject: Re: Serialization warnings
To: dev@cayenne.apache.org
Content-Type: text/plain; charset=ISO-8859-1

+1 for doing this for the generate-always classes.

Undecided about the generate-once subclasses.

On Thu, Jun 14, 2012 at 10:06 AM, Michael Gentry <mgentry@masslight.net> wrote:
> Going back to https://issues.apache.org/jira/browse/CAY-1622 ...
>
> How about if Cayenne Modeler has an option for the following choices:
>
> A) Generate @SuppressWarnings("serial") in the super/sub classes.
>
> B) Generate a a calculated serialVersionUID in the superclass and
> default the value in the subclass:
>
> _Foo: protected static final long serialVersionUID = [calculated];
> Foo: protected static final long serialVersionUID = _Foo.serialVersionUID;
>
> This way the superclass will get a new value should the attributes
> change and the default value for the subclass will be the same as the
> superclass, but the developer can override this if they wish.
>
> Thoughts?
>
> mrg