Should I use chained functions in Java?

Question

From time to time, I'll have a class in Java that takes a multitude of parameters, however, sometimes when I am creating an object of this class, I don't need to use all the parameters. As of now, I usually set the parameters to null or 0 depending on the type. However, would it be easier if I just created chained methods to set certain fields in the class?

So, instead of:

MyClass someInstance = new MyClass(param0, null, null, 0, null, param5);

Have something like this:

MyClass someInstance = (new MyClass()).setParam0(param0).setParam5(param5);

Does this go against OOP or Java's usual paradigm?

Answer 1

This is the perfect place for the Builder Pattern.

MyClass someInstance = (new MyClassBuilder())
    .setParam0(param0)
    .setParam5(param5)
    .build();

Answer 2

while it's not particularly uncommon to see the chains...

the chained methods approach (to me) suggests that you are dealing with a class that is a data blob where all/most fields/members are publicly accessible and mutable, and that there really is no separation of members and interface (e.g. little substance beyond public accessors). these classes tend not to manage their dependencies correctly, and when they do, it is often quite costly compared to initialization proper. the abstractions are also likely to be weak.

at that point, the class has really meandered from good OOD because they have typically violated multiple OOD principles/concepts.