Which configuration will have priority: XML, Java, or annotations?

The configuration priority in Spring Framework is usually distributed as follows, starting from the highest priority:

1. Annotations (@Autowired, @Value, etc.): Have the highest priority because they are directly in the code and most specific to the element.
2. Java configuration (@Configuration, @Bean): Next in priority. Used for programmatic creation and configuration of beans.
3. XML configuration (<bean>, context:component-scan, etc.): Has the lowest priority among these three.

If the same bean or property is configured in multiple ways, preference will be given to the configuration with a higher priority.

For example:

• If a bean is defined in XML and also created using @Bean in Java configuration, Spring will use the version from Java configuration.
• If a property of a bean is specified using @Value (annotation) and also in an XML file or Java configuration, the value from @Value will be used.

However, it is important to understand that Spring allows flexible combination of different approaches. It is good practice to predominantly use one style (for example, Java configuration or annotations) to reduce complexity. XML configuration is often used in inherited projects.

It is also worth noting that the priority can be influenced by the order of loading configuration files and specific application context settings. But the general rule of priority remains: Annotations > Java configuration > XML configuration.