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 2650: Issue: create and delete are always confirmed
Issue 3596: Unclear on ProxyAgentController
Issue 3597: Unclear on ProxyAgentController
Issue 4249: Issue with the "Basic Concepts" section

Issue 2650: Issue: create and delete are always confirmed (corba_tmn-rtf)

Click here for this issue's archive.
Nature: Uncategorized Issue
Severity:
Summary:
Summary: This is an issue for the "CORBA/TMN Interworking RTF":
 
 In the OSI Facilities, the specification potentially allows to have
 unconfirmed ManagedObject creations/deletions, whereas in Q3/OSI they
 are always confirmed. The OSI Facilities should thus explicitly say that
 for creation and deletion operations, LinkedReplyHandler and
 EndOfRepliesHandler cannot be null object references, otherwise an
 exception should be raised (e.g. BAD_PARAM).
 

Resolution:
Revised Text:
Actions taken:
May 10, 1999: received issue

Discussion:


Issue 3596: Unclear on ProxyAgentController (corba_tmn-rtf)

Click
here for this issue's archive.
Nature: Uncategorized Issue
Severity:
Summary:
We are looking on the implementation of the JIDM interfaces. The class
ProxyAgentController is unclear to us. How we can make decision on
Graceful destruction looking on the return value of the
destruction_is_allowed operation of ProxyAgentController? What is meant
by the 'terms and conditions' addressed by the Criteria return value of
that operation. It will be a greate help if you could clear our doubts.

Resolution:
Revised Text:
Actions taken:
May 4, 2000: receieved issue
May 4, 2000: received issue

Issue 3597: Unclear on ProxyAgentController (corba_tmn-rtf)

Click
here for this issue's archive.
Nature: Uncategorized Issue
Severity:
Summary:
We are looking on the implementation of the JIDM interfaces. The class
ProxyAgentController is unclear to us. How we can make decision on
Graceful destruction looking on the return value of the
destruction_is_allowed operation of ProxyAgentController? What is meant
by the 'terms and conditions' addressed by the Criteria return value of
that operation. It will be a greate help if you could clear our doubts.

Resolution:
Revised Text:
Actions taken:
May 4, 2000: closed issue

Issue 4249: Issue with the "Basic Concepts" section (corba_tmn-rtf)

Click
here for this issue's archive.
Nature: Clarification
Severity: Minor
Summary:
The "Basic Concepts" section contains an explanation of terms to be used throughout the document. I find that the definition of some terms and their later use in the same Basic Concepts section appear, at first glance anyway, to be ambiguous or contrary to each other thus throwing me into a terrible state of confusion! 

Namely, 8th paragraph (included below) does not seem to enable me to understand the 12th paragraph that I also include. Namely, the problem is the words in brackets do not seem correct in the context. 

1) Managed domains are sometimes referred to as "agents" and "managed object domains." while manager domains are sometimes referred to as "manager applications" or simply "managers." 

2) When a manager (agent) gains access to a managed object domain (manager domain), it is said . . . . 

If it is a case that one can read the sentence using the bracketed words as the alternative that is ok, i.e., 

form 1) When a manager gains access to a managed object domain, it is said . . . . 

form 2) When an agent gains access to a manager domain, it is said . . . . 

But, in my view it is not a consistent use of the brackets as earlier in the same paragraph bracketed words are used as an alternative name for something they follow (an equivalent entity) (see paragraph 6 same section) as opposed to a different entity.

Resolution:
Revised Text:
Actions taken:
April 5, 2001: received issue