Hi all,
I am actually trying to understand the configuration of BLC site application [broadleaf archetype ] and I have few questions in this.
Looking in to the web.xml of site-war module we have the following application config files specified under patchConfigLocation context param, and what I understand is that the MergeContextLoaderListener is merging all these configuration to create a global configuration.
classpath:/bl-open-admin-contentClient-applicationContext.xml
classpath:/bl-cms-contentClient-applicationContext.xml
/WEB-INF/applicationContext-security.xml
/WEB-INF/applicationContext.xml
Now the DispatcherServlet's init param has the following config files.
classpath:/applicationContext-servlet-cms-contentClient.xml
/WEB-INF/applicationContext-servlet.xml
So the resultant WebApplicationContext of the DispatcherServlet is basically a combination of all the above config files (4 files defined under patchConfigLocation which form the global scope and the 2 under DispatcherServlet).
But what I do not understand is that not even all the above files put together has the full blown configuration of the application.
Ex: the aop configuration being used for Transaction management and repricing of order every time we invoke a method on CartService or OrderService, complete entity configuration, work flow config etc... are not present in the above mentioned files
So how come the other config files are being pick up by the container (which are not mentioned in web.xml).
Thanks,
Avinash
This forum is in readonly mode and serves as an archive of old information. All posting, registration and commenting abilities have been turned off. To get help, the Broadleaf team reguarly monitors the broadleaf-commerce tag on Stack Overflow so please ask your questions there.