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 <[email protected]> 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<[email protected]?body=SIGNOFF%20openmrs-devel-l>from > OpenMRS Developers' mailing list _________________________________________ To unsubscribe from OpenMRS Developers' mailing list, send an e-mail to [email protected] with "SIGNOFF openmrs-devel-l" in the body (not the subject) of your e-mail. [mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l]
