11g 1.3 provides a new Serializable class warning ?

Question

We have an adf swing app we moved to version 1.3
we now get this warning in most of the app classes:
Serializable class contains non-serializable fields: [contactX]
this is an example class as basic as you can get that extends JDialog and It uses another class. The warning wants to mark ContactX.class as transient ?
This should not require the "private transient" Keyword as it has nothing to do with Jdialog being Serializable.
Is this produced for some reason due to changes in use of the adf binding or
has something changed that could impact the application now or in the future or is this warning in error?
public class ContactXDialog extends JDialog {
private ContactX contactX;
}

Answer 1

Ok I think I understand your confusion better now.
- JDialog implements Serializable
- You extends JDialog, so ContactXDialog also implements Serializable
- Serialization implies the serialization of all fields, so contactX is a serialization candidate
- Now there's two possibilities.
1. contactX is calculable, meaning you can compute it back at runtime if needed, this is often the case of cached or lazy fetched values. Then you can make the field transient, effectively removing it from the serializable candidates
2. contactX must be set, then it must be serialized, therefore it must be Serializable as well. So the only option here is to have ContactX class implement the Serializable interface.
The warning offered the easiest way out, albeit likely a problematic one, to add the transient modifier.
Regards,
~ Simon