Legacy Issue Number: 3984
Source: Hewlett-Packard ( Peter Furniss)
This is a possible issue arising from 3425 - I don't think the current text
says what we meant.
On looking through the current OTS text (00-09-04) I found the interaction
table deems ADAPTS/UNSHARED and ADAPTS/EITHER are invalid. This would seem
to seriously modify messaging capabilities, since it would mean that only
REQUIRE objects can be invoked via routing from within a transaction (this
is assuming that InvocationPolicy is irrelevant and unchecked when there is
no active transaction). There is no mapping for what used to be
ALLOWS_UNSHARED and ALLOWS_EITHER. Given that many objects will have ADAPTS,
and EITHER is the default InvocationPolicy, this will severely restrict the
use of routed invocations.
Surely this is not what was intended. Checking the earlier drafts, it was a
side-effect of removing ALLOWS to be (mostly) replaced by ADAPTS. ADAPTS had
always had invalid with unshared or either, but allows was valid.
Reported: OTS 1.0b1 — Mon, 23 Oct 2000 04:00 GMT
Updated: Fri, 6 Mar 2015 20:57 GMT
OTS11 — Allowed InvocationPolicy and OTSPolicy interactions
- Key: OTS11-29
- OMG Task Force: Additional Structures for OTS RTF