Should we always have a zero-argument constructor in a Class?

Question

Should every Java class have a zero-argument constructor?

Answer 1

No

If it makes no sense to create an instance of the class without supplying any information to the constructor then you need not have a zero-argument constructor.

A good example is java.awt.Color class, whose all ctors are argumented.

Answer 2

No, it doesn't make sense to always create zero argument constructors, the following scenarios are examples where it makes sense to provide at least a-some-argument-constructor

1. Required dependencies that the class itself cannot create.
2. There are no senseful defaults for the properties.

Cases where you want to have/need a zero-argument constructor:

1. You want to comply to the JavaBeans specification (makes sense for simple data objects).
2. All fields can be initialized using senseful defaults.
3. You want to use a framework that needs it.

One of the mis-arguments for having a zero-argument constructor in my opinion is a long list of arguments. For that there are better solutions than accepting to initialize an object that isn't in a safe state after creation:

1. Using the Builder pattern.
2. Provide specialized container objects to configure an instance via the constructor.
3. Provide multiple constructors where the base arguments of each one are the required parameters that cannot have defaults assigned.