Issue 2649:  ptc/99-02-02: Impl side mapping and the POA (ada-rtf)
Source:  (, )
Nature:  Uncategorized Issue
Severity: 
Summary: Summary: Has the Ada RTF considered the generation of a POA_<interface_name> 
 package for the Impl side mapping? 
 
 This is the approach taken by the C and C++ mappings, and has 
 the advantage of keeping the Impl package completely free of 
 code required by the ORB.
 

Resolution: Discussion:
This approach was considered during the initial mapping development in 1995. It was
rejected because it would preclude inheritance of a servant type from a servant mapped
from a parent IDL interface, a use case considered much more important than the
advantage cited. The use of “tie” implementations can achieve the cited advantage.
Disposition: Closed, no change
Revised Text: 
Actions taken:
May 10, 1999: received issue
January 12, 2010: closed issue
Discussion: 

End of Annotations:=====
From: "Oliver Kellogg" <Oliver.Kellogg@vs.dasa.de>
To: <ada-rtf@omg.org>
Subject: ptc/99-02-02: Impl side mapping and the POA
Date: Mon, 10 May 1999 13:23:47 +0200
X-Msmail-Priority: Normal
X-MIME-Autoconverted: from quoted-printable to 8bit by emerald.omg.org
id HAA24297

Has the Ada RTF considered the generation of a POA_<interface_name> 
package for the Impl side mapping? 

This is the approach taken by the C and C++ mappings, and has 
the advantage of keeping the Impl package completely free of 
code required by the ORB.

In Ada parlance, for an IDL interface of the form:

  interface A {
     void doit ();
  };

a package POA_A is generated:

  with PortableServer;

  package POA_A is

     type Object is new PortableServer.Servant_Base with null record;

     type Object_Access is access all Object'Class;

     procedure Init (Self : Object_Access);
        -- subject to standardization

     procedure doit (Self : access Object) is abstract;

  private
     -- spec private part and package body are
     -- implementation defined.

  end POA_A;


The user or IDL compiler can then generate an Impl package,

  with POA_A, A;

  package A.Impl is

     type Object is new POA_A.Object with private;
        -- the "with private" is implementation dependent

     procedure doit (Self : access Object);

  end A.Impl;
  -- Further declarations in package spec and
  -- package body are user defined.


Thanks,

Oliver M. Kellogg
--
DaimlerChrysler Aerospace
e-mail: oliver.kellogg@vs.dasa.de


Reply-To: <victor.giddings@mail.ois.com>
From: "Victor Giddings" <victor.giddings@mail.ois.com>
To: <ada-rtf@omg.org>
Cc: "'Nick Roberts'" <nick.roberts@acm.org>
Subject: Proposed Resolution for Issue 2649 - for comment
Date: Thu, 18 Aug 2005 17:59:23 -0400
Organization: Objective Interface System
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
Thread-Index: AcWkQBeA99SRGERTQSGk2mROkTJaTw==


OMG Issue No:  2649
Title:  Impl side mapping and the POA
Source:
DaimlerChrysler Aerospace, Oliver M. Kellogg, Oliver.Kellogg@vs.dasa.de
Summary:
Has the Ada RTF considered the generation of a POA_  package for the Impl
side mapping? 
This is the approach taken by the C and C++ mappings, and has the advantage
of keeping the Impl package completely free of  code required by the ORB.
Discussion:
This approach was considered during the initial mapping development in 1995.
It was rejected because it would preclude inheritance of a servant type from
a servant mapped from a parent IDL interface, a use case considered much
more important than the advantage cited. The use of "tie" implementations
can achieve the cited advantage.
Disposition:    Closed, no change


Victor Giddings                     Chair, Ada RTF
victor_giddings@omg.org