Juliano, What you describe as changeable service factory parameters sounds interesting. It seems like this should be possible without making the module definitions mutable. You would have to create your own service model which knows when the CSI has to be reconstructed (i.e. when the parameters change). Further you'd need a reference to the factory parameters you want to change.
Note that this split of service factory and factory parameters will not exist in the same form in HiveMind 2 anymore. There will simply be a service implementation constructor (see http://tinyurl.com/ytox2o) which given a service point constructs a CSI for it. You'll be able to provide your own implementations for this interface. Of course as part of the XML support there will still be an implementation of this interface supporting service factories with parameters. Regards, --knut On 1/25/07, Juliano Viana <[EMAIL PROTECTED]> wrote:
That is misleading indeed... What I wanted to do (and missed the support for ) was to be able to change service factory parameters and configurations at runtime. Of course, once you change the parameters of a service point's factory then the service has to be reconstructed. That is not s big problem for the singleton service model - since the service is lazily constructed, it can be reconstructed at any time anyway. In the end I think it is possible to do all this without a fully writable registry api - but as I said, it will involve advising some parts of the registry and producing an "enhanced" version of hivemind. - Juliano. Knut Wannheden wrote: > Juliano, > > As currently envisioned modifications to the registry after > construction time, i.e. at runtime, would still not be possible. The > new API is somewhat misleading in that respect which I think is > another good reason to change it. > > --knut
