This type of documentation (in which we specified from where this method is called, and where we actually explain what the method does naming private attributes totally irrelevant for someone using the API), is hardly maintainable. If at some point we use this method to do something else (we will), we should come here and add it to Javadoc? And when we refactor and stop doing that thing, it'll be impossible we remember that we must come here and update the javadoc. This method does override another method, and its super javadoc should be enough in most of cases.

I know that we're trying to avoid past mistakes, and I agree Javadoc and documentation are very important, but it think we should not overreach. Maintaining all this javadoc is going to be very time consuming, which would be ok if it was useful, but, IMO, I don't think that's the case.