Breaking the Spring Framework's code: dynamic bean definition
From time immemorial, one of the core things we did with our Spring-based Java applications was fitting the business logic into beans and making them properly interact with each other. We wrote context.xml files, later on @Configuration classes and even injected dynamic properties from configuration files into them, but still each bean was statically defined in the context. What should we do in the situation, where we'd like to get a collection of beans, sharing similar structure but being fully customizable by the properties (also in terms of cardinality)? Is copy-pasting the same code for each bean number of times required to do so, or perhaps there's some other way? Join me and find out! :)
