Issues for OMG Common Management Facilities Revision Task Force

List of issues (green=resolved, yellow=pending Board vote, red=unresolved)

List options: All ; Open Issues only; or Closed Issues only

Issue 502: ManagedSets::Set::intersection_members() should return iterator
Issue 503: p. 45, Para 3.5.7.8 editorial
Issue 504: p. 45, Para 3.5.7.8, editorial
Issue 505: ManagedSets::Set::union_member() should return an iterator
Issue 506: PolicyRegions::PolicyRegion::verify_policy() should return iterator
Issue 507: PolicyRegions::PolicyRegion::get_policy_failures()
Issue 508: Add usage warning for Identification::Labeled::set_label()
Issue 509: Change exception conditions for ManagedSets::Set::add_object()
Issue 510: ManagedSets::Member::add_backref()
Issue 511: uehavior of how_many in ManagedSets::Member::get_backrefs()
Issue 512: Add usage warnings to ManagedSets::Member::remove_backref()
Issue 513: uehavior of how_many in ManagedSets::Set::get_members()
Issue 514: how_many and regular_expression in ManagedSets::FilteredSets::find.
Issue 515: Constrain the inherited behaviors in the Instance Management servic
Issue 516: Missing default for instance manager"s inheritedcreate_object oper.
Issue 517: set_default_initialization and set_default validation (add behavior
Issue 518: Behavior specification for duplicate and nil inputs (lookup_labels)
Issue 519: how_many should be unsigned in iterators"next_n operation
Issue 520: ManagedInstances::BasicInstanceManager::create_object()
Issue 521: Criteria for ManagedInstances::InstanceManager (create_object)
Issue 522: Validation policies set vie set_validation_policy
Issue 523: Policies::PollicyObject needs method returning CORBA::InterfaceDef
Issue 524: Allow Object::_nil() input to PolicyObjectAdmin set_default operat.
Issue 525: Add flag to add_object() to disable invocation of m->add_backref()
Issue 526: how_many should be unsigned wherever it appears
Issue 527: Correct editorial error in Para 3.6.6.2
Issue 528: move_to_policy_region() and add_to_policy_region()
Issue 529: PolicyRegions::create_object()/PolicyRegionsInstanceManager
Issue 530: Initialization and validation policies in add_instance_manager()
Issue 531: Specify use for default initializations and validation policies
Issue 532: Disallow Object::_nil() as input to add/remove initialization
Issue 533: Specify behavior when default policies are removed via remove oper.
Issue 540: "with" and "without" as only valid ids
Issue 541: _pr_backrefs operations added to Policies::PolicyObjectAdmin interf

Issue 502: ManagedSets::Set::intersection_members() should return iterator (xcmf-rtf)

Summary: Size of m_list will be as large as it could be for for get_members operation. Omission of an iterator for intersection_members is inconsistent--> scalability problems

Summary: Add following Sentence: " The initial size of m_list is determined by the how_many argument. The rest of the Member objects, if any, can be retrieved using the returned.."(see file)

Summary: chang line 1261 to " CORBA 1.2 standard exceptions and SysAdminException::ExInvalid."and add following paragraph immediately following line 1261 (--->see file "issue504)

Summary: Omission of iterator for union_members is inconsistent and may lead to scalability problems, since m_list is as large as it could be for get_members operation. (proposed change--> see file)

Summary: A new iterator interface needs to be defined for data of type PolicyResult

Summary: Should return iterator. A iterator interface needs to be defined for data of type PolicyResult. Edits to define this new iterator are included

Summary: Nothing prohibits a client from performing actions like Creating an object with unique label, adding it to a managed set and invoking set_label to change objects" label to duplicate other obj

Summary: Proposed change requires that object labels be explicitly unique in space and time. A wording change to Para 3.6.4.2 is suggested

Summary: Add usage warning and define behavior. It"s important to clarify the intended use of add_backref and warn about indiscriminate use  which would lead to corruption of set-member relationship graph

Summary: We believe that how_many should be of type long. We suggest that if how_many is greater/equal to total number of backrefs they should be returned in s_list parameter and as OBJECT_NIL

Summary: same as issue 510 plus the fact that objects that inherit from both ManagedSets::Set and CosLifeCycle::LifeCycleObject inherit the latter"s remove operation.

Summary: how_many should be of type unsigned long. It makes sense to allow negative numbers for a quantity.

Summary: how_many should be of type unsigned long. If it is greater than or equal to total number of members that match filter criteria, all of those members should be returned in ml_list parameter

Summary: The explicit proscriptions should appear in the "unique behavior of inherited Interfaces" sections within the description of the Instance Management Service and elsewhere as appropriate.

Summary: ManagedInstances::Instancemanager specifies the name "nested initialization" which is paired with a boolean "true" or "false".. We recommend a default of FALSE.

Summary: If input object is not associated with instance manager then the set default methods will go ahead and invoke add_initialization or add_validation. Result:ExObjNotFound exception is not raised.

Summary: ManagedSets::FilteredSet::lookup_labels does not specify behavior for udplicate entries in m_list parameter, CORBA::Object::_nil() entries in m_list, Empty m_list parameter

Summary: how_many should be type long. If it is greater/equal to the total number of objects maintained by iterator object, all backrefs should be returned in output list parameter, no exception raised

Summary: The labelid exception is impossible to implement. The signature of create_object does not provide for raising the ExNotUniqueLabel exception!

Summary: We believe that the list criteria should be processed atomically. (see file)

Summary: They will be enabled by default. Para 3.7.4.7 doesn"t state whether or not the validation policy assigned to the specified instance manager is enabled or disabled by default. Specify..

Summary: There is no straightforward way to compare fully-scoped interfacetype name returned by get_policy_driven_object_type() with interface returned by get_instances_interface()

Summary: The specification does nor currently state how _nil() inputs to the set_default methods are to be handled.

Summary: When an object adds itself to a set, there is no need to for the set to notify original object to add back reference to the set. Skip unnecessary over-the network method invocation..(file)

Summary: Parameter how_many should be of type unsigned long. It does make sense to allow negative numbers for what is supposed to be a cardinal quantity. Reference: CRs submitted by NEC

Summary: P. 55 para 3.6.6.2 lines 1615 1nd 1616 replace RepresentativeBasicInstanceManager and RepresentativeInstanceManager with PolicyRegionsInstanceManager

Summary: The spec doesn"t specify behavior for what to do when an object that already is member of a PolicyRegion is moved or added to that PolicyRegion again.

Summary: The newly created PolicyRegion should be added to its PolicyRegionsInstanceManager which supports the PolicyRegionsInstanceManager interface.

Summary: They must be registered with the instance manager being added. This appears to be an oversight.

Summary: The spec provides methods for setting default initialization and validation policies for instance managers, but never describes the intended use for them.

Summary: Disallow Object::_nil() as an input to add/remove initialization and add/remove validation. An explicit proscription should be added fore the sake of interoperability.

Summary: What happens when policy that is default policy is removed via one of the "remove" operations? The specification does not say.

Summary: make "with" or "without" the only valid ids to go along with "initialization policy" and "validation policy" kinds within find_factories operation supported by ManagedInstances::Library in

Summary: Add "add_pr_backref","remove_pr_backref", and get_pr_backrefs" operations to Policies::PolicyObjectAdmin interface