One more constructor for ApplicationLauncher?

[manifoldronin]

Would it make sense to add another constructor for ApplicationLauncher along the line


ApplicationLauncher(ApplicationContext startupContext, ApplicationContext context)


The reason being that an application might want to load the main context from filesystem, yet still want to benefit from fast loading the startup context.

Cheers.

[Keith Donald]

But the contexts -- at least the bean defintions -- for both startup and use are all ready loaded at that point, right?

[manifoldronin]

But the contexts -- at least the bean defintions -- for both startup and use are all ready loaded at that point, right?


That's one damn good point, isn't it? :oops:

How about this then:


ApplicationLauncher(ApplicationContext startupContext, ContextProvider provider)

where ContextProvider would be a callback that actually loads the context?

Thanks.