Hi Tom Apologies for the delay.
Please see below to understand what I was referring to. I just did a pull and build on Sunday May 21 ~17:00 CET. Regards Nathan samples $ pwd /Users/.../git/opendaylight-git/controller/opendaylight/md-sal/samples ls toaster/src/main/yang-gen-sal/org/opendaylight/yang/gen/v1/http/netconfcentral/org/ns/toaster/rev091120/ $YangModelBindingProvider.java MakeToastInput.java ToasterBuilder.java ToasterRestockedBuilder.java $YangModuleInfoImpl.java MakeToastInputBuilder.java ToasterData.java ToasterService.java DisplayString.java RestockToasterInput.java ToasterListener.java WheatBread.java FrozenBagel.java RestockToasterInputBuilder.java ToasterOutOfBread.java WhiteBread.java FrozenWaffle.java ToastType.java ToasterOutOfBreadBuilder.java WonderBread.java HashBrown.java Toaster.java ToasterRestocked.java samples $ mvn clean … samples $ ls toaster/src/main/yang-gen-sal/org/opendaylight/yang/gen/v1/http/netconfcentral/org/ns/toaster/rev091120/ ls: toaster/src/main/yang-gen-sal/org/opendaylight/yang/gen/v1/http/netconfcentral/org/ns/toaster/rev091120/: No such file or directory So, the generated code is placed into the src/main directory, which is not what one would expect with Maven builds in general. > On 17 May 2017, at 13:46, Tom Pantelis <tompante...@gmail.com> wrote: > > > > On Wed, May 17, 2017 at 5:42 AM, Nathan Sowatskey <nat...@nathan.to> wrote: > Thank you Tom. Hopefully this will help Arlindo. > > I am afraid I didn’t check, but I thought that the documentation that Arlindo > looked at did refer to the location of the code that you gave below. My bad > for not looking. > > In any case, the code is, as Tom says, in /opendaylight/md-sal/samples. > > I last looked at that in detail about six months ago. As an example, it is > better than nothing, but incorrect in some ways. For example, it generates > code into the src/main directory, rather than the Maven convention of target. > > The generated code goes under target - the pom derives from binding-parent > and is up-to-date. I just updated the step-by-step wiki to be in-line with > the current code (conversion to blueprint etc). What else is incorrect about > it? We should fix anything that's incorrect. > > > What you might want to do, Arlindo, is look at the Nodes application and > track how that works through the various layers. > > Regards > > Nathan > > > On 11 May 2017, at 16:56, Tom Pantelis <tompante...@gmail.com> wrote: > > > > Nathan, > > > > The toaster example in core tutorials was started but abandoned (as you can > > tell :(). This > > https://wiki.opendaylight.org/view/OpenDaylight_Controller:MD-SAL:Toaster_Step-By-Step > > is the best one that I know of. The code is in the controller project > > under /opendaylight/md-sal/samples. This wiki hasn't been updated in a > > while so parts of it are out-of-date, specifically the parts about the > > config system as the toaster example has since been converted to blueprint. > > So for the latest, please see the code in /opendaylight/md-sal/samples. > > I'll make a note to update the wiki at some point. > > > > Tom > > > > On Thu, May 11, 2017 at 10:04 AM, Arlindo L. M. Jr <arlindo...@gmail.com> > > wrote: > > Hi Nathan... > > > > Thanks for your help... > > > > I'm trying follow the tutorial (toaster), but, I can't find the > > files/folders when I do the "git clone" in the repository... Like the link > > explains: > > https://wiki.opendaylight.org/view/Controller_Core_Functionality_Tutorials:Tutorials:Starting_A_Project > > > > There are some comments in this link, from Michael V... > > https://git.opendaylight.org/gerrit/#/c/40316/2 > > I think that it was removed, or will be reformulated, i dont know... > > > > Another option? > > > > Thanks in advance... > > > > = = = > > > > 2017-04-30 8:19 GMT-03:00 Nathan Sowatskey <nat...@nathan.to>: > > Look for the Toaster example as a guide. > > > > Regards > > > > Nathan > > > > > > > On 29 Apr 2017, at 15:56, Arlindo L. M. Jr <arlindo...@gmail.com> wrote: > > > > > > hi folks... > > > > > > Someone, maybe, have some samples of how to develop a module, internaly > > > to controller? > > > Or, maybe, how to write and integrate a module with the controller? > > > I want to write an application to colect, and manipulate, some QoS data > > > (e.g., ttl, ping time) retrieved from the underlying hosts and switches. > > > I would like this app to work, or run near/inside, of the ODL controller. > > > Not an app to using the REST Api, in the northbound layer... > > > > > > Any help is welcome. > > > > > > Thanks in advance. > > > > > > -- > > > almjr > > > _______________________________________________ > > > controller-dev mailing list > > > controller-dev@lists.opendaylight.org > > > https://lists.opendaylight.org/mailman/listinfo/controller-dev > > > > > > > > > > -- > > Arlindo Luis Marcon Junior > > Internet Web Page: http://lattes.cnpq.br/6483462042489662 > > Irati - Paraná - Brasil > > > > The information contained in this e-mail, and any attachment, is > > confidential and is intended solely for the use of the intended recipient. > > Access, copying or re-use of the e-mail or any attachment, or any > > information contained therein, by any other person is not authorized. If > > you are not the intended recipient please return the e-mail to the sender > > and delete it from your computer. Although we attempt to sweep e-mail and > > attachments for viruses, we do not guarantee that either are virus-free and > > accept no liability for any damage sustained as a result of viruses. > > > > _______________________________________________ > > 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