Serializable Object.class

Question

public class RegisterRequest implements Serializable {

    @NotNull(message = "Register may not be null")
    private Object register;

}

I got codeSmell from sonarLing SonarLint: Make "data" transient or serializable.

Because I have Object.class I can't add in this class implements Serializable also I can't transient because I need this object serialize.

How I can fix this codeSmeel by sonar lint?

My recommendation is to deactivate the rule. Trying to enforce serializable types at compile time via declarations contradicts common practice and will turn out to be impossible in a lot of scenarios. See [this answer](https://stackoverflow.com/a/31117279/2711488) and also [this comment](https://stackoverflow.com/questions/31115005/whats-the-best-way-of-ensuring-a-function-argument-is-serializable/31117279#comment50251549_31115005) — Holger, Oct 05 '20 at 12:23

score 0 · Answer 1 · answered Sep 30 '20 at 08:30

0

The thing with Object fields is, those do not implement the Serializable interface. SonarQube is saying that you're trying to serialize a field, in this case Object register which does not implement the interface. For your register field you should use a custom class which implements the Serializable interface.

Because of this SonarQube is telling you that you should either let Object implement the Serializable interface (which you can't) or mark it with transient.

answered Sep 30 '20 at 08:30

Danilo Jakob

71
1
6

If I use custom register field I will get same error in custom class also – Valdy B Sep 30 '20 at 08:58
So you made a class `Register` and implemented the `Serializable` interface in that class? – Danilo Jakob Sep 30 '20 at 09:02
My register class also will have Object.class – Valdy B Sep 30 '20 at 09:29
@ValdyB with Object.class this won't work. You need to declare a class Register which holds your information. You can't use Object.class. – Danilo Jakob Sep 30 '20 at 09:31
For my case I need only Object.class – Valdy B Sep 30 '20 at 09:43
@ValdyB What you could do would be create a class `CustomeObject` which extends the `Object` class and there implement the `Serializable` interface. Then you have the same behaviour as the `Object` class. – Danilo Jakob Sep 30 '20 at 14:00

Serializable Object.class

1 Answers1