Issue 3939: An assembly is always mono-vendor ??? (components-ftf) Source: Open Networks Engineering (Mr. Jean-Christophe Dubois, jcd(at)one.com) Nature: Uncategorized Issue Severity: Summary: Because the interfaces between the Assembly and the container/componentServer/servantActivator is not defined, these ones have to be vendor specific. Because the ExecutorSegmentBase and the HomeExecutorBase are not specified a component is always container specific. As a result an assembly provided by one vendor can only speak to container/componentServer/servantActivator provided by the same vendor and the container can only run (even in Java???) components that have specifically ported to it. The conclusion is that it is not possble to build an asembly that combine components build on different CCM platform. All of the component have to be ported to a single CCM platform. Is it what is intended? Resolution: see below Revised Text: In ptc/99-10-04, replace the section 69.9 between pages 69-327 and 69-334 by the content of the ccm/2001-10-03 document. In ptc/99-10-04 section 69.3.2.10 page 69-264, set the cross reference “See section 69.9.5 on page 332” to the section number 69.9.8 and the new related page. Actions taken: October 5, 2000: received issue May 13, 2002: closed issue Discussion: The section 69.9 of the ptc/99-10-04 document does not define the ServerActiva- tor, ComponentServer, Container, ExecutorSegmentBase and HomeExecutorBa- se interfaces. Then, deployment could only be done in a vendor specific manner. In order to allow the deployment of applications on different CCM platforms, these interfaces must be defined in the CORBA Component Model specification. The section 69.9 of the ptc/99-10-04 document must be replaced by the content of the ccm/2001-10-03 document which defines the ServerActivator, Component- Server, and Container interfaces. These interfaces are defined in a generic and portable way allowing interoperability between deployment middleware provi-ded by various vendors. As each creation operation takes a sequence of ConfigValue objects as parameter, each vendor could add its own configuration values without breaking the specification. However standard configuration values should be collected and defined in a new RFP dedicated to advanced CORBA component deployment. The definition of the ExecutorSegmentBase and HomeExecutorBase interfaces must be resolved according to the Issue 3651. End of Annotations:===== From: "Jean-Christophe Dubois" To: Cc: Subject: An assembly is always mono-vendor ??? Date: Thu, 5 Oct 2000 17:19:26 -0400 Organization: Open Network Engineering 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: $@5e9'c%!!