Pranjal, The archetype generates initial suggested directories. There's really no rules on how to organize the code - in the end it's your code and up to you. The toaster example has the RPC implementation in a provider bundle and an RPC user in a consumer bundle but it's just an example. If you have RPCs, the user/consumer may just be the NB restconf.
Tom On Fri, Jun 8, 2018 at 12:52 AM, Pranjal Sharma <pranjalsharma3...@gmail.com > wrote: > Hi All, > > I hope you are doing well. I am fairly new to the OpenDaylight framework > and trying to get a finer understanding of the MD-SAL infrastructure. To > get started, I am trying to develop the complete *Toaster* example from > scratch using *odl-startup-archetype*. I am following the tutorial: > https://wiki.opendaylight.org/view/OpenDaylight_Controller: > MD-SAL:Toaster_Step-By-Step. > > Before starting the Toaster example, I have developed a simple MD-SAL > application that had a provider but no in-project consumer. So, I used to > put all the yangs in *api* directory, and the providers in the *impl* > directory generated by the odl-startup archetype. > > With Toaster, I am struggling to understand where to place the consumer in > the directory structure generated by the odl-startup-archetype. Does the > Consumer go into the *impl* directory too (probably in a sub-directory > for consumer), as it is exposing some functionality itself? I have seen the > code of Toaster on GitHub, but that didn't clarify my doubt. > > I will really appreciate any help regarding this. I look forward to your > response in the matter. > > > Thanks, > Pranjal Sharma > > > > _______________________________________________ > controller-dev mailing list > controller-dev@lists.opendaylight.org > https://lists.opendaylight.org/mailman/listinfo/controller-dev > >
_______________________________________________ controller-dev mailing list controller-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/controller-dev
