gnodet wrote:
> 
> On 12/14/06, RNobrega <[EMAIL PROTECTED]> wrote:
>>
>>
>> Both ideas are great, but lack the "future-proof" feature we would
>> like to have; btw, we also thought of jmx, exposing methods to change
>> the parameters, but this would also be an "a priori" effort
>>
> 
> What if all servicemix components that use the xbean deployer were
> able to load additional spring configuration files ? Such a file could
> contain the definition of a BeanFactoryPostProcessor , which would be
> automatically applied to all deployed xbean.xml files.
> Such a configuration could be done in the components.properties file
> which is currently by components to retrieve default configuration values.
> Imho, this would be generic enough to be reused in other cases ...
> This would also ensure that all properties can be modified but I think it
> would
> be easier to use than using reflection.  Thoughts ?
> 
> -- 
> Cheers,
> Guillaume Nodet
> 
> 

Yes, looks very promising, but I'm not sure I can guess all the
ramifications right now...
-- 
View this message in context: 
http://www.nabble.com/listeners-in-container-and-MessageExchange-tf2815007s12049.html#a7873201
Sent from the ServiceMix - User mailing list archive at Nabble.com.

Reply via email to