For project like this one - it would be cumbersome, but proper Java is also solving the problem. Currently we write code without all throws definitions, because

For project like this one - it would be cumbersome, but proper Java is also solving the problem. Currently we write code without all throws definitions, because those are handled by Spring-like monsters or other libraries, but having method definied with LockedEx, NullPointerEx etc. is even more friendly as doc generation. Funny, but I don’t like Java that much, but it’s one of those languages also solving documentation problems here. Yes I know it’s "faster-development" to have type instead of additional definition attributes, but I think the problem would be also solved.