The only reason I can see for us to keep the context resources in the omod is because the API is meant to be functional without a web context. However, the services (context-based way of manipulating data) are always located in the API, and we provide the Context object in the API of OpenMRS core. This makes it hard to decide exactly what should go where.
How do we draw the line between API and web / webapp in core? Is there a need, besides the fact that we have historically separated concerns this way, to keep separate projects for each module? Why not just use different packages in the same module if it's going to be difficult to run tests? Jeremy Keiper OpenMRS Core Developer AMPATH / IU-Kenya Support On Mon, Nov 7, 2011 at 3:06 PM, Rafal Korytkowski <[email protected]> wrote: > Hey, > > Mavenized modules consist of the api and omod subprojects. This setup > is not quite right since one cannot write context sensitive tests in > the api subproject. The reason is that resources for creating the > Spring Context are in the omod subproject, thus context sensitive > tests must be placed there. I believe we should reorganize things and > make it possible to write tests in the api subproject. Does anyone > know reasoning behind the current "strange" structure? Would there be > any problems if we changed that? > > -Rafal > > _________________________________________ > > 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] > _________________________________________ 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]
