Multiple there means with each module load over the lifetime of your module in openmrs. Only one time per spring restart though. Spring is restarted once at openmrs startup (only once whether you have 1 or 20 modules loaded) and then each time a module is added by an admin later.
Ben On Wed, Apr 25, 2012 at 1:35 PM, Dave Thomas <pihd...@gmail.com> wrote: > Sorry, i was confused by the javadoc for this method: > > * Called after spring's application context is refreshed , this > method is called multiple times > * i.e. whenever a new module gets started and at application startup. > > At application startup or when i add a new module in 1.7+, this method is > only called *once for a given module activator, against the newly loaded > context including all services from all modules, right? > > The 'multiple' in the javadoc means 1 call per module? > > d > > > On Wed, Apr 25, 2012 at 10:28 AM, Darius Jazayeri <djazayeri+...@gmail.com > > wrote: > >> Using the pre-1.7 module activator framework, the service layer is >> typically *not* available when your activator's started() method is >> called. If your other module requires htmlformentry, then HFE's started() >> method will be guaranteed to be called first though. >> >> In 1.7+ you can use the new activator's contextRefreshed() callback >> (which is wonderful) and happens whenever any module is started/stopped. >> >> -Darius >> >> On Wed, Apr 25, 2012 at 9:58 AM, Dave Thomas <pihd...@gmail.com> wrote: >> >>> Hi. question, maybe directed at Ben -- >>> >>> I have a use case where i have a module registering custom htmlformentry >>> tags through HtmlFormEntryService.addHandler(..) during module startup. >>> This seems to be working fine when called from my other module's started() >>> method in its Activator (extends BaseModuleActivator) in a couple of server >>> restarts, however, i just want to make sure that there might not be a race >>> condition here. >>> >>> So, is this working because all services from all modules should be >>> available when any module's started() method is called, or am I just >>> getting lucky by having htmlformentry load before my other module? >>> >>> d >>> ------------------------------ >>> Click here to >>> unsubscribe<lists...@listserv.iupui.edu?body=SIGNOFF%20openmrs-devel-l>from >>> OpenMRS Developers' mailing list >> >> >> ------------------------------ >> Click here to >> unsubscribe<lists...@listserv.iupui.edu?body=SIGNOFF%20openmrs-devel-l>from >> OpenMRS Developers' mailing list > > > ------------------------------ > Click here to > unsubscribe<lists...@listserv.iupui.edu?body=SIGNOFF%20openmrs-devel-l>from > OpenMRS Developers' mailing list > _________________________________________ To unsubscribe from OpenMRS Developers' mailing list, send an e-mail to lists...@listserv.iupui.edu with "SIGNOFF openmrs-devel-l" in the body (not the subject) of your e-mail. [mailto:lists...@listserv.iupui.edu?body=SIGNOFF%20openmrs-devel-l]
