On Thu, 2003-02-27 at 11:01, Robert McIntosh wrote: > I'm toying with Fortress now, coming from ECM, and I am currently using > just the default container. Other than a few exceptions about the > context not finding info about the role manager on startup, it runs just > fine. After I get most of my initial work done and all my stuff works, I > plan on extending the default container to provide a couple of features > and would like some ideas here. > > The first thing I want to be able to do is implement the Reconfigurable > lifecycle. I've had requests from clients to be able to change the > configuration without restarting the app. My first thought it to have a > Monitor component watch the config file(s) for changes and then follow > this process: >
In Plexus I'm implementing the tried and true Service Configurator pattern. Part of series of patterns that are part of Doug Schmidt's ACE patterns: http://www.cs.wustl.edu/~schmidt/patterns-ace.html The Service Configurator pattern is down there on the page. This pattern embodies the primary requirement of the project I'm working on in that the train cannot stop, ever. I'm going to implement it simply as a set of components which I'm sure can be resuable across containers. The Service Configurator pattern can also be found in Pattern Oriented Software Architecture (POSA) v2 p75. Well worth the 40 bucks. > > jvz. > > Jason van Zyl > [EMAIL PROTECTED] > http://tambora.zenplex.org > > In short, man creates for himself a new religion of a rational > and technical order to justify his work and to be justified in it. > > -- Jacques Ellul, The Technological Society --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
