Issue 4318: Remote SignalSets                                                                                                                                                                                       (ots-structs-ftf)
Source: University of Newcastle upon Tyne (Dr. Mark Little, m.c.little@ncl.ac.uk)
Nature: Uncategorized Issue
Severity: 
Summary: Section 2.2.1 says:
> If a SignalSet fails to produce Signals (e.g., it is physically remote
from
> the
> ActivityCoordinator and fails to respond to invocations), then the
> completion status of the
> Activity is set to CompletionStatusFailOnly, and the ActivityCoordinator
> should act
> accordingly.

We never actually intended SignalSets to be used remotely. I'd like to
recommend (on behalf of ourselves and IBM) that we use the local idl keyword
to make this explicit.

Resolution: This issue is addressed by issue 4256, close issue
Revised Text: 
Actions taken:
May 21, 2001: received issue
May 2, 2003: closed issue
Discussion: 

End of Annotations:=====
From: "Mark Little" <mcl@arjuna.com>
To: "XOTS FTF" <ots-structs-ftf@omg.org>
Cc: <issues@omg.org>
Subject: Fw: Remote SignalSets
Date: Mon, 21 May 2001 12:01:05 +0100
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Content-Type: text/plain;
	      charset="iso-8859-1"
X-UIDL: MQCe9<E=e9F3k!!0GF!!

> Section 2.2.1 says:
> If a SignalSet fails to produce Signals (e.g., it is physically
> remote
from
> the
> ActivityCoordinator and fails to respond to invocations), then the
> completion status of the
> Activity is set to CompletionStatusFailOnly, and the
> ActivityCoordinator
> should act
> accordingly.

We never actually intended SignalSets to be used remotely. I'd like to
recommend (on behalf of ourselves and IBM) that we use the local idl
keyword
to make this explicit.

Mark.

----------------------------------------------
Dr. Mark Little (mark@arjuna.com)
Transactions Architect, HP Arjuna Labs
Phone +44 191 2064538
Fax   +44 191 2064203


From: "Mark Little" <mcl@arjuna.com>
To: "XOTS" <ots-structs-ftf@omg.org>
Subject: FTF meeting summary
Date: Wed, 18 Jul 2001 10:05:44 +0100
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6600
X-MIMEOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
X-Filter-Version: 2.1 (cheviot3)
Content-Type: text/plain;
	      charset="iso-8859-1"
X-UIDL: *%D!!CL[d9H0jd9D]:!!

Just a quick note to report on the meeting we had at Danvers. We
managed to
work through all of the issues that were reported prior to Danvers,
though
some have come up since. A brief summary of the issues we discussed,
and the
resolutions follows (the individuals who will write up the final
proposed
resolutions are also indicated).

Proposal for 4318: closed issue because of 4256. [Mark Little to write
up.]


From: "Mark Little" <mcl@arjuna.com>
To: "XOTS FTF" <ots-structs-ftf@omg.org>
Subject: Proposal for 4318
Date: Tue, 31 Jul 2001 16:54:38 +0100
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Content-Type: text/plain;
	      charset="iso-8859-1"
X-UIDL: bD"!!RHC!!PPa!!=iDe9

I'd like to close this issue assuming that issue 4256 makes it clear
that
all system SignalSets are not remotely invocable.

Mark.

----------------------------------------------
Dr. Mark Little
Transactions Architect, HP Arjuna Labs
Email: mark@arjuna.com | mark_little@hp.com
Phone: +44 191 2064538
Fax  : +44 191 2064203