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

Clarify patient dashboard error ServletException: There is no patient with id: '9347'

    XMLWordPrintable

    Details

    • Complexity:
      Low

      Description

      If the user gets to the patient dashboard page by a bad link (or a bug I suppose) the user gets a descriptive but ugly error message.

      Instead of showing the raw ServletException, the PatientDashboardController.java and patientDashboardForm.jsp page should instead show a message in an error box and show the findPatient portlet for the user to do another search.

      See automated error report below:

      Version: 1.8.2 Build 21762

      Started Modules: serialization.xstream v0.2.5, logic v0.5, reporting v0.6.1, htmlformentry v1.7.3, xforms v4.0.4, reportingcompatibility v1.5.4.1, formentry v4.5.9.2, htmlwidgets v1.5.6.2

      Summary:
      javax.servlet.ServletException: There is no patient with id: '9347'

      Description:
      Stack trace:
      org.openmrs.web.controller.patient.PatientDashboardController.renderDashboard(PatientDashboardController.java:63)
      at [ignored] ...
      javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
      javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
      org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
      <snip>

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              jasper.vandemalle Jasper Vandemalle
              Reporter:
              bwolfe Ben Wolfe
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 30 minutes Original Estimate - 30 minutes
                  30m
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 2 hours, 45 minutes
                  2h 45m