I agree the naming conventions / practices also contribute to the verbosity, but you would name the AbstractErrorCorrectingModalDialogueFactory the same way in any OOP language, if this name describes it best.
though to respond to your assertion, I actually think @floppydisk got to my point in a much quicker manner than I could. I don't think I'd need to express such a thing in a more expressive language. I'm not talking about the naming convention, I'm talking about how Java forces you into a version of OOP that requires you to use a litany of "design patterns" get anything done. A more expressive language would be able to capture the same idea without the litany of java classes, interfaces, and generics that come with java.