|
|
|
They are in two different idea modules, which mean they will likely end in two different web applications, with two different contexts: what is a set of config files made for, if you treat every bean from every set just the same way? Beans of a set should not "see" beans of another set.
Davide,
Well here is the confusion... in IdeaSpring what is called "Config Set" should be called "Group" considering your definition of a config set. Then what is a "group" for?? I mean, what is it useful for, if putting config files into a single group or into multiple groups is just the same thing?
Config sets are similar to idea's module groups. The need here is for something to isolate different contexts in the same project.
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What if you really want applicationContext-A1.xml from module A, to refer to a bean X in applicationContext-B.xml from module B ?