Grigore: unfortunately, this is a little too strong. If we do this then we end up in cases where we have getters and setters for variables that are really obvious what they do and then we have something like:

    /**
     * The ID of the state
     */
    private StateId stateId;

    /**
     * Gets the state ID
     */
    public StateId getStateId() {
        return stateId;
    }

    /**
     * Sets the state ID
     */
    public void setStateId(StateId stateId) {
        this.stateId = stateId;
    }

Which doesn't really add any value. Similarly some private methods also need javadocs because it's not clear from looking at them what they do and the purpose they serve. So it's more a matter of where a comment is needed in order to provide readability and understanding of the method/class/field than it is about any kind of proscription. You just look at the method and kind of know whether it's needed.