Issues for CORBA/TMN interworking RTF mailing list

To comment on any of these issues, send email to corba_tmn-rtf@omg.org. (Please include the issue number in the Subject: header, thusly: [Issue ###].) To submit a new issue, send email to issues@omg.org.

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

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

Issue 1405: RDN to NameComponents mapping issue
Issue 2625: CORBA/TMN Interworking Issue: Initial EventPortFactory

Issue 1405: RDN to NameComponents mapping issue (corba_tmn-rtf)

Click here for this issue's archive.
Nature:
Severity:
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 ?
 

Resolution: :NameComponent,
Revised Text:
Actions taken:
June 1, 1998: received issue

Discussion:


Issue 2625: CORBA/TMN Interworking Issue: Initial EventPortFactory (corba_tmn-rtf)

Click
here for this issue's archive.
Nature: Uncategorized Issue
Severity:
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??
 

Resolution:
Revised Text:
Actions taken:
April 28, 1999: received issue

Discussion: