I often create a "template" superclass for such garbage (at least until Lombok, when I can use Lombok). These methods are still available by looking at inherited properties.
However, a class with so many properties can be called up by some kind of refactoring, depending on your actual needs - this is a lot to keep track of.
(You can also filter the list, but this is dangerous because if you hide, say, get* , you can remove real methods from the view.)
source share