What is good about writing Java code in XML format as in Spring configuration?



As a .Net developer who started Java dev for less than a year, one thing that puzzles me is the wide usage of Spring configuration file. Let me clarify:


In the case of an IoC container, I haven't seen the community being interested in setting up their Catalog/Module/Etc. through xml config in any other platform than Java.


The XML configuration is usually used as a highly verbose alternative to calling constructors/factory methods. This clearly is a disadvantage over code as is not type-safe, too verbose, and not indexable in IDEs (e.g. Find Usages of a Method)


Other IoC frameworks such as Autofac support xml configuration but in those non-java platforms XML config is unpopular.


My Question:


Is there a best/practice design principle, etc backing this choice of XML configs for IoC or its merely a historical habit?


No comments:

Post a Comment