|
From: Alef A. <al...@jt...> - 2003-12-15 23:49:00
|
> > Suppose there's two app contexts, A and B. In A there's bean 1 > > depending > on bean 2 in B. In B, there's bean 3, depending on bean 4 in > A. This is circular, however, I still want to somehow be able > to do this. Basically the BeanFactory stops processing bean > definitions if it can't find a bean reference that might be > located in a sibbling context. I tend to state that the bean > definition creation should postponed until all > sibbling-contexts are resolved and maybe then try it again? > Any suggestions (or just 'no not possible' will do as well :) > > This should be possible already. In case of multiple context > definition files, all the bean definitions from all files get > loaded first - *then* context initialization and bean > pre-instantiation begins. The only thing that doesn't work, > because it arguably can't work, is two FactoryBeans > referencing each other. Can you give some details on what > doesn't work in your scenario? I'll ask joost if I can't more details... He's probably got a couple of example context files lying around... Alef |