I had forgotten that I had asked this question before and you guys had responded. So I think I'm good enough for now. I think I know what I need to do, I can worry about persistence with component upgrades later.. thanks :)
On Sat, Feb 27, 2010 at 8:58 AM, Ryan Moquin <[email protected]> wrote: > Out of curiousity, I've been working on a management portion for our > services. I think I finally figured out the best way to do what I need in > that regard but I do have one question to help me finish. If you create an > MBean for an SE so that you can customize an SU at runtime. What's the best > way to persist those changes between servicemix restarts? I have an SU > that gets deployed with default values, but should be able to be changed at > runtime. I wasn't sure if anyone on the SMX team could recommend the best > way to do this, or if there are some unit tests in SMX that I could look at > for suggestions on how I can do this. I wasn't sure if I could get away > with writing a property file somewhere, of if there is a way to modify the > xbean.xml at runtime and the deactive/activate the SU to reload those > changes? > > Any suggestions would be helpful. Thanks!! > > Ryan >
