Bug 352431 - Bind configuration artifacts to a region
Summary: Bind configuration artifacts to a region
Status: ASSIGNED
Alias: None
Product: Virgo
Classification: RT
Component: runtime (show other bugs)
Version: 3.0.0.M06   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 enhancement (vote)
Target Milestone: 3.6.0.RELEASE   Edit
Assignee: Chris Frost CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 352217
Blocks:
  Show dependency tree
 
Reported: 2011-07-19 06:01 EDT by Chris Frost CLA
Modified: 2012-07-19 13:18 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Frost CLA 2011-07-19 06:01:55 EDT 
Each region has it's own ConfigAdmin. This works well to keep configuration separated. The RAM should be updated to record this and enforce all configuration to belong to a region, the region that it's ConfigAdmin bundle is in.
Comment 1 Chris Frost CLA 2011-07-19 06:26:13 EDT 
This will also require improvements to the MBeans published by the deployer. They should include some information about which region each configuration is in. My initial though is that the ObjectName should be extended to have a 'region=' field in it.
Comment 2 Nobody - feel free to take it CLA 2011-07-19 06:28:58 EDT 
Targeting 3.5 release.