Broadleaf Commerce Discussion Forums

Hi Guys,

Is there a reason xml configuration was used in the demo project instead of using annotations (@Configuration)

Would it be a good idea to still use annotation for any new configuration ?

Broadleaf provides a powerful context merge process that happens on app startup. For example, we define the following bean in a Broadleaf JAR:



If you were to have the following in your own applicationContext.xml file:



The actual bean that would get passed to Spring would be:



You can see which beans/properties support merging in default.properties (though it is a bit hard to understand).

I'm not entirely sure that the @Configuration annotation would handle this with as much flexibility as we provide, but to be honest, I haven't researched that particular annotation very much.

Hope that helps.