Details
-
Bug
-
Resolution: Won't Do
-
Major
-
None
-
None
-
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