I'm quite happy to announce Dynamic-JMS to our readers. Dynamic-JMS is the first published effort that allows developers to use JMS dynamically in the OSGi environment. The task was quite complicated, but relatively small, which in turn made a solution possible after all. Now you can update Connection Settings, Upgrade Broker client or simply switch Messaging Brokers while the application is running, the listeners still listening and sessions stay valid - Well, every thing you deserve to have in a dynamic environment like OSGi.

Make sure to check the project, and try to use it if it doesn't make sense to you restarting the whole application for the sake of changing a connection string. And please, let us know what you think, or simply contribute some code that makes it even a better experience to use JMS dynamically in the OSGi environment.

P.S. Having implemented the first concept for running Java Web Services dynamically in the OSGi environment (Dynamic-WS), the first project that simplifies the dynamic use of JPA components in the OSGi environment (Dynamic-JPA), and now the first concept for running JMS components in the OSGi environment (Dynamic-JMS), you can bet that soon enough the first concept for running REST services dynamically in the OSGi environment will become available, so stay tuned!