Wondering if it makes sense for the best practice for serialized classes to a generated serial number instead of just suppressing the warning? Currently in Ofbiz there are lots of examples of the suppression in place but only one generated serial number (org.ofbiz.common.authentication.api.AuthenticatorException).
My brief understanding is that Java will make use of the generated serialVersionUID when it is determining if the definition of a class has changed for deserialization rather than using reflection. We have been working on cleaning up warnings in the source code and this is one that I am just now considering for clean-up. Thoughts? -- View this message in context: http://n4.nabble.com/Usage-of-SuppressWarnings-serial-tp361041p361041.html Sent from the OFBiz - Dev mailing list archive at Nabble.com.
