Interworking Between CORBA and TMN Systems Avatar
  1. OMG Specification

Interworking Between CORBA and TMN Systems — Closed Issues

  • Acronym: TMN
  • Issues Count: 2
  • Description: Issues resolved by a task force and approved by Board
Open Closed All
Issues resolved by a task force and approved by Board

Issues Summary

Issues Descriptions

CORBA/TMN Interworking Issue: Initial EventPortFactory

  • Key: TMN-6
  • Legacy Issue Number: 2625
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: How does a CORBA manager get a JIDM::EventPortFactory reference ? In
    order for a manager to create an EventPort would it:

    A) i) resolve the ProxyAgentFinder (eg, resolve_initial_references())
    ii) obtain a reference to a ProxyAgent
    iii) obtain a factory finder from the ProxyAgent via
    get_domain_factory_finder()
    iv) use the EventPortFactory returned by iii) to create an EventPort
    for the domain

    • OR -

    B) i) resolve the EventPortFactory (eg. resolve_initial_references())
    ii) invoke create_event_port() with some additional Critieria that
    describes which domain is being accessed??

  • Reported: TMN 1.0b1 — Wed, 28 Apr 1999 04:00 GMT
  • Disposition: Resolved — TMN 1.0
  • Disposition Summary:
  • Updated: Sat, 7 Mar 2015 05:46 GMT

RDN to NameComponents mapping issue

  • Key: TMN-4
  • Legacy Issue Number: 1405
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Issue regarding RDN to CosNaming::NameComponent mapping (page 4-76): How
    should an OSI naming attribute be mapped to a CosNaming::NameComponent,
    when the ASN.1 attribute syntax is a SEQUENCE containing OPTIONAL and/or
    DEFAULT elements ?

  • Reported: TMN 1.0b1 — Mon, 1 Jun 1998 04:00 GMT
  • Disposition: Resolved — TMN 1.0
  • Disposition Summary:

    :NameComponent,

  • Updated: Sat, 7 Mar 2015 05:44 GMT