cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kelven Yang" <>
Subject Review Request: Finalize componentContext.xml/nonComponentContext.xml content organization to be plugin friendly
Date Thu, 04 Apr 2013 22:14:03 GMT

This is an automatically generated e-mail. To reply, visit:

Review request for cloudstack and Chip Childers.


With removal of component auto-scanning, all components are needed to configure in XML files.
For OSS deployment, component declarations will be in applicationContext.xml and componentContext.xml,
for non-OSS deployment, component declarations will be in applicationContext.xml and nonossComponentContext.xml

OSS/non-OSS common components should all go to applicationContext.xml, OSS or non-OSS specific
components, or if there are OSS or non-OSS specific adapter configurations, they should go
to componentContext.xml or nonComponentContext.xml respecitively.

If you add a big feature module, organize all components for the module into its own section.

This addresses bug CLOUDSTACK-1917.


  client/tomcatconf/ 17725f0 
  client/tomcatconf/ 2a4a29f 
  client/tomcatconf/ 13004c3 
  utils/src/com/cloud/utils/component/ PRE-CREATION 



manual test is done for both OSS/non-OSS


Kelven Yang

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message