Details
-
Story
-
Status: Closed
-
TBD
-
Resolution: Fixed
-
None
-
None
-
Medium
-
Order Entry 1.10 Iteration 2, Order Entry 1.10 Iteration 3
Description
MDS provides support for different versions of OpenMRS within a single module. It is achieved thanks to splitting module's API into jars: mds-api-common.jar, mds-api-1.7.jar, mds-api-1.9.jar. Currently all jars are put on the classpath, even if all we need on OpenMRS 1.6 is mds-api-common.jar. A module developer must be really careful to prevent using any classes from mds-api-1.7.jar or mds-api-1.9.jar on OpenMRS 1.6. In order to make it easier to structure modules this way, I propose to provide a new tag in config.xml:
<conditionalResources> <resource> <path>lib/mds-api-common.jar</path> <omrsVersion>[1.6)</omrsVersion> </resource> <resource> <path>lib/mds-api-1.7.jar</path> <omrsVersion>[1.7)</omrsVersion> </resource> <resource> <path>lib/mds-api-1.9.jar</path> <omrsVersion>[1.9)</omrsVersion> </resource> </conditionalResources>
Such a declaration would result in loading:
mds-api-common.jar on OMRS 1.6,
mds-api-common.jar and mds-api-1.7.jar on OMRS 1.7 and 1.8
mds-api-common.jar, mds-api-1.7.jar and mds-api-1.9.jar on OMRS 1.9
Gliffy Diagrams
Attachments
Issue Links
- is depended on by
-
HTML-515 Add support for drugOrder in OpenMRS 1.10
-
- Closed
-
- is related to
-
META-228 Cannot import a concept containing a mapping in OpenMRS 1.9
-
- Closed
-
-
TRUNK-5213 Load Spring resources conditionally based on missing module(s)
-
- Closed
-
- relates to
-
TRUNK-4378 Modules using conditional loading should not fail on older versions
-
- Closed
-