Convention over configuration (English)
The application written in Java EE programming language is often cluttered with configuration files which hold many settings providing essential flexibility for the application. Deployment descriptors, persistence unit configuration files, database settings or many framework configuration files are all examples of this phenomenon. If the configuration had to be written from point blank every time it would make the development much more complicated and the development period would be severely prolonged. This is where convention over configuration principle comes to rescue.
Convention over configuration, commonly referred to as coding by convention, is a software design paradigm which effectively tries to decrease number of decisions developers need to make thus simplifying the development process without losing flexibility. This design paradigm declares that developers only need to reconfigure the configuration files if they desire behavior which differs from the conventional(default) one.
Such design paradigm is beneficial not only for decreasing the software development period but also for liberating developers from thoroughly studying configuration manuals from cover to cover. If some unconventional behavior is required only general configuration structure and specific configuration information have to be considered and learned.