On Thu, Oct 28, 2010 at 6:50 AM, Simone Tripodi <simone.trip...@gmail.com> wrote: > That's why I wouldn't follow the option #2; but please, explain me > which are the side effects of that design, so I can avoid to repeat > the same mistake in the future. >
If you make the config objects immutable, you can just keep the config references around and skip the copying in the reconfigure() method. I don't think it would be difficult to implement things this way. We don't want to let the JMX stuff dictate our API too much. The JMX stuff can be less "elegant" for sure. Consider it to be just a UI layer on top of our stuff. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
