I'm actually working in a huge project providing a server and client spring application. The client - for runtime concerns - is using a xml configuration of its beans but the server does not, leading to an immense start up time (at least 20 minutes) due to the classpath scanning. Which is ok for deployment in its production environment, but is a huge overhead for all the developers waiting for the server to start up may be several times per day.
My Question:
Is there any "easy" way to switch from classpath scanning to a static configuration?
I'm thinking of some kind of xml generation for instance. To me, it should be possible to generate a static configuration file the same way the configuration is done via classpath scanning at start up. Are there any concerns I don't know preventing something like that? Does there exist any kind of generator like that?