Well, is it?
I have a hard time believing that.
Not sure, what is so hard to believe. Does "handle" mean something
specific to you that isn't compatible with my line?
[...]
final Job jobAnnot=method.getAnnotation(Job.class);
assert jobAnnot != null;
final Schedule lifecycle=jobAnnot.value();
[ ... further code doesn't use jobAnnot ...]
That's about what I meant by "handle".
jobAnnot is merely a handle for the result of method.getAnnotation(...).
It is then used twice (assert and retrieving some value) and then
forgotten. If it weren't for the assert, you might have written:
final Schedule lifecycle= method.getAnnotation(Job.class).value();
(this particular assert seems rather useless anyway, as the NPE would
definitely be thrown, anyway. assert makes more sense, if failure of
the checked condition could otherwise go unnoticed until much later.)
I admit that your coding style isn't really as "functional" as I had
believed it to be from your complaint about so many "final"s...
Most of my code would look quite similar, but I wouldn't bother
adding finals, where the variable is only used in the following two
or three lines of code. I would, however, still care to make those
variables final whose scope contains a complete loop or more than
say 10 lines of code.
