If you supply all the configurations to the TDO bean, that'll force the configurations to be loaded before the TDO bean is loaded. Probably just subclass the TDO bean to add a single throwaway property that you can pass a <list>of configurations to.
I don't know anything about Transfer, but it seems like that'd work, even with the kludge factor it leverages. cheers, barneyb On Feb 6, 2008 12:40 AM, Sean Corfield <[EMAIL PROTECTED]> wrote: > Here's an interesting dilemma. I'm using Brian's TDO bean injector and > I have it auto-load with lazy-init="false" and that works just fine. > Now I have multiple Transfer XML files and so I figured I could force > those to be added by using lazy-init="false" (and factory-method to > force calls to addConfig() on transferConfiguration). > > Anyone see the problem? Right, the non-lazy beans are initialized in a > random order so some configurations are applied but the TDO bean > injector is created which creates Transfer and so no more > configurations can be applied... > > What I'm after is some way to force init a bunch of beans and have > another bean initialized before my application actually runs. > > In one app using Mach-II I just added a plugin with a setter for the > TDO bean injector which forces the right sequence (because autowiring > is performed after ColdSpring initialization but before the app runs). > This works even for remote requests because Mach-II initializes via > Application.cfc. > > Any suggestions / tricks for doing this automatically in other applications? > > > -- > Sean A Corfield -- (904) 302-SEAN > An Architect's View -- http://corfield.org/ -- Barney Boisvert [EMAIL PROTECTED] http://www.barneyb.com/ Got Gmail? I have 100 invites.
