Not really. I do understand transient, but I'd have to store other data to be able to recreate the Property when needed. It just seems like an unnecessary step unless there's a reason that Propertys aren't serializable.
-Lon On Tue, May 14, 2019 at 3:59 PM John Huss <johnth...@gmail.com> wrote: > Does this help? > > > https://stackoverflow.com/questions/910374/why-does-java-have-transient-fields > > > On Tue, May 14, 2019 at 5:20 PM Lon Varscsak <lon.varsc...@gmail.com> > wrote: > > > Any reason we can't have Property be Serializable? I have situations > where > > I will keep references to properties in a web page (like for dynamic > > columns) and my framework serializes those things (or errors out if it's > > not serializable). I originally solved this with having my own Subclass > be > > Serializable, but now with protected constructors I'm getting errors. > > > > Thoughts? > > > > -Lon > > >
