I was trying to understand what was going inside the Atlas module earlier and I noticed a lot of functions that were defined but not called. However, these functions would need to called if the module must work. Where is this happening, and how does the reference application learn about a particular module?
I think I figured out what’s happening.
The methods I was referring to belong to the class AtlasData, which was being used in the AtlasService, which i used throughout the module. However, on startup AtlasModuleActivator uses AtlasService to set the properties of AtlasData. That was an impulsive post, sorry about that 
There’s a class in the reference application repo called ConfigureAtlasNotificationProducer, so maybe reference application contains some basic info about other modules?
1 Like