Uploaded image for project: 'OpenMRS Core'
  1. OpenMRS Core
  2. TRUNK-4946

Discard all changes to an object when retiring/voiding/unretiring/unvoiding it

    XMLWordPrintable

Details

    • New Feature
    • Status: Closed
    • TBD
    • Resolution: Won't Fix
    • None
    • None
    • None
    • Undetermined

    Description

      Refactor the AOP methods for retireXXX(), unretireXXX(), voidXXX(), and unvoidXXX() methods to discard any changes to the object and only save changes to the voided/retired, voidedBy/retiredBy, dateVoided/dateRetirede and voidReason/retireReasom fields. As a result, the methods will return the original object with only void/retire fields changed instead of the object passed in to the method.

      Update the Javadoc for each retireXXX(), unretireXXX(), voidXXX(), and unvoidXXX() method to state clearly that any changes to the object will be lost.

      Include a unit test to prove that changes made to an object (other than to void/retire fields) when retiring, voiding, unretiring, or unvoiding are lost.

      Method to use to discard changes:

      AOP Handlers:

      Gliffy Diagrams

        Attachments

          Issue Links

            Activity

              People

                jwnasambu Juliet Wamalwa
                wyclif Wyclif Luyima
                Votes:
                0 Vote for this issue
                Watchers:
                12 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved: