Option 1: A couple of threads/articles talked about pointing the configuration areas to different Blueprint files. This was not the best idea for us because we were going to need to create ~100 different Blueprint files and corresponding configurations (bad maintenance tail).
Option 2: We were thinking how we could using the config.ini files for each container. This seemed like a better idea, but we run into the same maintenance tail as with the Blueprint files.
We came to the conclusion that we wanted to be able to pass a single/simple parameter (container ID derived from the OS) when we would start the containers. The development/integration path we are going to take is to start each container programmatically from a bundles Activator object. We would read in the server configuration file, change the container's ID based on the parameter, and start the container.
My questions are:
- Is this a good idea?
- Has anyone done this already?
- What should we be concerned with implementing containers this way?
- Are we completely lost? (don't be shy if you think we are, we are engineers and have no feelings)
We do feel like we are getting close to a strong stable implementation of XS with OSGi, but we are really in the infancy of understanding both technologies. Any and all help/guidance is greatly appreciated.