That is exactly how it is split, sorry for the confusion. Should have put an extra sentence in there describing the dependency!
Ben On Wednesday, April 18, 2012, Burke Mamlin wrote: > Are there two modules? An *event* module seems appropriate to introduce > an event bus that other modules can register with to send or list for event > (e.g., providing the event management that an enterprise container like > JBoss would); however, exposing these events as an ATOM feeds seems out of > scope for an event bus module – i.e., I was expecting an *event* module > to introduce an event bus and an *atomfeed* module that uses the event > bus for the particular use case of exposing changes as ATOM feeds. > > -Burke > > 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]
