https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/MDSAL-413 mdsal <p>We have migrated blueprint extension from the controller project. We need to adjust it to work with MD-SAL interfaces and to occupy different namespaces.</p> <p>As part of this, we need to split up the extension into at least two parts, because it combines generic concepts (like static-reference) and binding concepts (like rpc-service).</p> MDSAL-413

Add blueprint component

New Feature Medium Resolved Won't Do Unassigned Robert Varga Tue, 8 Jan 2019 15:34:27 +0000 Sat, 22 Feb 2020 07:15:41 +0000 Sat, 22 Feb 2020 07:15:41 +0000 blueprint 0 1 <p>The basic mindset behind blueprint goes directly against MD-SAL's view of immutable objects. Specifically, hides all dynamic services behind proxies, isolating us from the Service Registry. Hence we cannot use the registry to exchange state &#8211; which defeats the point of having the service registry.</p> <p> OSGi Declarative Services use static binding (by default) and allow us to expose component lifecycle, so that it can be correctly responded to.</p> <p> We therefore remove any pretense we are endorsing blueprint &#8211; because we are not. Everybody should decompose their application properly and use DS for OSGi.</p> Development Rank 0|i03lwf: