So, I kind of figured it out… In the past, I was creating my DataStoreLifeCycle with ComponentContext.inject() and it had some members which were @Injecte(d) - those were the guys that were failing to be instantiated. When I switched to simply @Inject my DataStoreLifeCycle into my DataStoreProvider, everything works fine.
So, with this new system, is there some reason that using ComponentContext.inject() would fail to load beans while @Inject would succeed? -Chris -- Chris Suich chris.su...@netapp.com NetApp Software Engineer Data Center Platforms – Cloud Solutions Citrix, Cisco & Red Hat On Oct 24, 2013, at 4:04 PM, SuichII, Christopher <chris.su...@netapp.com> wrote: > Darren, > > I’m switching my plugin over to use the new modularized Spring stuff you just > merged and there is something I’m still battling with. I have other beans > that were previously instantiated before my DataStoreProvider which get > injected into the provider, lifecycle, etc. So, those beans need to be > instantiated before the DataStoreProvider. How can I ensure those beans are > created and setup before the DataStoreProvider does? > > -Chris > -- > Chris Suich > chris.su...@netapp.com > NetApp Software Engineer > Data Center Platforms – Cloud Solutions > Citrix, Cisco & Red Hat >
