The idea is that the event module would be updated if that method is added. The user would just need to listen to the appropriate event or a new event key if need be. The idea is that the other module author then doesn't need to keep track of the API and/or know all possible method calls in depth in order to know when something is changed.
Ben On Wednesday, April 18, 2012, Wyclif Luyima wrote: > Since this will be using AOP, does it mean calls like > patientService.addIdentifier(Patient, Identifier)(this is hypothetical) > wouldn't be picked up by the event bus machinery, this is one of the > reasons why i tend to be against convenience/short hand calls on services > to create new entries via add/register() methods as sometimes we suggest > during design calls. > > Wyclif > > On Wed, Apr 18, 2012 at 8:39 AM, Ben Wolfe > <[email protected]<javascript:_e({}, 'cvml', '[email protected]');> > > wrote: > >> >> My spike this week is around setting up an "atom feed" of changes in >> openmrs. This will allow another system to ping openmrs periodically and >> know when new data is being entered or edited. (the wiki page for the >> atomfeed module <https://wiki.openmrs.org/display/docs/Atom+Feed+Module>is >> but a shell for now) >> >> Executive summary: >> >> - The module is just called "event" and we hope to integrate it to >> core eventually to prevent module devs from having to AOP for messaging >> - The module registers AOP around the services for now >> - The module exposes things like "Patient created" "patient updated", >> "concept deleted", etc >> - Other modules can register to be notified of these Events using >> either Spring or a simple java call >> >> You can see the longer api calls on the wiki page for the Event module: >> https://wiki.openmrs.org/display/docs/Event+Module >> >> I'd like to spend a few minutes on the design >> call<https://wiki.openmrs.org/display/RES/Design+Forum>today discussing >> this, but also feel free to voice ideas/opinions/outrage >> here as well. >> >> Ben >> >> ------------------------------ >> Click here to unsubscribe <javascript:_e({}, 'cvml', >> '[email protected]?body\x3dSIGNOFF%20openmrs-devel-l');> from >> OpenMRS Developers' mailing list > > > ------------------------------ > Click here to unsubscribe <javascript:_e({}, 'cvml', > '[email protected]?body\x3dSIGNOFF%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]
