It will be done on the BI level in the final product. Right now, just trying to quickly create something for a demo.
Thanks. Can you elaborate on the second reason for the Proxies? Why the fact that the Binding is specified as interfaces is an argument for working with a Proxy? -----Original Message----- From: controller-dev-boun...@lists.opendaylight.org [mailto:controller-dev-boun...@lists.opendaylight.org] On Behalf Of Robert Varga Sent: Monday, August 22, 2016 4:25 PM To: Sela, Guy <guy.s...@hpe.com>; mdsal-...@lists.opendaylight.org; controller-dev@lists.opendaylight.org Subject: Re: [controller-dev] [mdsal-dev] onDataTreeChanged() Proxies / LadyDataObject On 08/22/2016 02:11 PM, Sela, Guy wrote: > Hi, > > I see that when I get a DCN, the fields of the object that are DTOs, > are all actually Proxies. > > I guess this is done for performance reasons. That, and also the fact Java Binding is specified in terms of interfaces, not classes (except for typedefs). > Is there a way to register in "Eager" mode, which will give me real > objects and not Proxies? No. > I am trying to serialize/deserialize these objects, and doing it with > proxies seems impossible. Java-like serialization is inherently tied to a particular implementation. Perfoming the same task on the BI level, as suggested in previous threads is the correct approach. Bye, Robert _______________________________________________ controller-dev mailing list controller-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/controller-dev
