13 | 13 | * JSP file `retraction_protocol2.jsp` in `resources/personal/` is coupled to Javascript file `retraction_protocol.js`. Values for input case name/personal number and the number of items to be destroyed are retrieved from the HTTP response, and `retraction_protocol2.jsp` creates a template for a table of items to be destroyed, one row per item, and `retraction_protocol.js` calls servlet `RetractionFormServlet` with command "`GetProtocolInfo`" (currently identical to command "`GetCaseInfo`") to obtain a JSONObject with information on all cases for the patient in question, which is sent to function `rp.initializeProtocol(response)` to be inserted into the protocol template. The reason for the suffix "`2`" in the name of JSP file `retraction_protocol2.jsp`, is that most protocol wizards have an initial JSP file `retraction_protocol.jsp`, with input fields for information required to retrieve the protocol data, but this role is here taken by `retractionform.jsp`. |
14 | 14 | * Java servlet class/file `RetractionFormServlet.java` in `src/net/sf/basedb/reggie/servlet/` accepts `GET` requests for commands "`GetCaseInfo`", "`GetProtocolInfo`" (currently identical to "`GetCaseInfo`"), and "`ExportRetractData`", as well as `POST` request for command "`RegisterRetraction`". It accesses the database to retrieve the requested information, or update the contents, and sends the results back in JSON format. |