Hi Hugo and Wido,
Earlier we used to have components.xml from where a sysadmin could
enable/disable components for ex. a plugin.
Now we've applicationContext and other *Context xml files, but I see
them copied to WEB-INF/classes:
Heya Rohit,
Why would a sysadmin need to change this? They should be considered part of the
source code, any configuration should be done via the config in the database or
with the *.properties files.
Cheers,
Hugo
-Original Message-
From: rohityada...@gmail.com
Hi,
For what it's worth, I was under the same impression as Rohit - that
administrators would edit components.xml to fit their deployment.
See for example this snippet from Extending CloudStack Networking [1]:
Generally, it is expected that the cloud administrator will configure
components.xml
Hey Hugo!
On Tue, Feb 26, 2013 at 2:55 PM, Hugo Trippaers
htrippa...@schubergphilis.com wrote:
Heya Rohit,
Why would a sysadmin need to change this? They should be considered part of
the source code, any configuration should be done via the config in the
database or with the *.properties
On Tue, Feb 26, 2013 at 2:55 PM, Hugo Trippaers
htrippa...@schubergphilis.com wrote:
Heya Rohit,
Why would a sysadmin need to change this? They should be considered part of
the source code, any configuration should be done via the config in the
database or with the *.properties files.
But
Hugo,
In the current model, components that are not needed by default are not
present in componentContext.xml. Just in case if you have not noticed, in
4.1, NiciraNvp bean is not enabled by default :). Admin needs to edit
componentContext.xml, to enable a optional component.
Thanks!
On 26/02/13
