-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Low
-
Affects Version/s: 3.5
-
Component/s: Core - Content REST APIs
If any of the notification related SOAP API methods are called with a page id that doesn't exist, they will throw a NullPointerException rather than the PageNotFoundException they are supposed to. This exception then triggers an attempt to render the 500 page, but that fails because SOAP methods will already commit their output before the 500 page begins rendering, which then throws an IllegalStateException.