I understand that but the binding DataBroker interface implements DataTreeChangeService w/o using the Extensible Object pattern so why can't the DOMDataBroker? It's inconsistent.
On Wed, Aug 24, 2016 at 7:13 AM, Robert Varga <n...@hq.sk> wrote: > On 08/24/2016 01:06 PM, Tom Pantelis wrote: > > Yes but accessing it via getSupportedExtensions isn't intuitive, hence > > the discussion. > > Well, it follows the Extensible Object pattern, which really is the only > feasible way to provide extensibility without breaking API contracts in > face of multiple competing contracts and forwarding classes... > > Bye, > Robert > >
_______________________________________________ controller-dev mailing list controller-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/controller-dev
