Uploaded image for project: 'Magnolia'
  1. Magnolia
  2. MAGNOLIA-2723

(to check) New servlets not picked up or initialized properly without a restart

    XMLWordPrintable

Details

    • Bug
    • Resolution: Won't Do
    • Major
    • None
    • None
    • core
    • None

    Description

      I just registered a new servlet in my Magnolia instance, and it seemed that, even though a new instance of ServletDispatchingFilter is matching the request, the servlet instance isn't initialized and ready to operate. Restarting Magnolia solved the issue.

      Another issue is that if the servlet class can't be loaded, the wrapping filter is still active, thus throwing ugly NullPointerExceptions at the user when a matching request is issued.

      Checklists

        Acceptance criteria

        Attachments

          Activity

            People

              pbaerfuss Philipp Bärfuss
              gjoseph Magnolia International
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Checklists

                  Bug DoR
                  Task DoD