@sunbiz, @n_nehete, we should start figuring out how code written in OWAs can integrate more closely with the existing OpenMRS reference application.
In particular, I think an OWA needs to be able to create app definitions and extension points (i.e. this tutorial step shouldn't require going the administrator to do anything.
I propose we make the module aware-of the App Framework module, and support a new section in manifest.webapp (I guess under activities) where the OWA author would define app templates, apps, and extensions exactly like is currently done by putting json files under /omod/src/main/resources/apps/.
The OWA module should register and unregister these apps and extensions when an OWA is added/removed.
The alternate approach is to think of the OWA module as part of the underlying platform, and allow other modules to register callbacks when an OWA is added/removed. Then the appframework module would become aware-of the OWA module. (This may be more consistent with our future direction.)