In earlier 7.1 releases, if the JadeRestService class processRequest method was called by user logic and the call was not part of the JADE REST service web message handling framework, a JADE crash could have resulted; for example, when creating a transient instance of a JadeRestService subclass and calling the processRequest method. (This occurred because the JADE REST service had not been initialized and the logic assumed that it had.)
To enable manual testing of JadeRestService methods, the handling has been changed to allow such a call, as follows.
The REST service will be initialized if it has not been already, unless the application is already attached to a JADE Web Service Manager.
Exception 11126 (A Rest Service method was called but the service was never initialised) will result.
If the JadeRestService class reply method is called and its processing is not associated with a received web message, exception 11127 (JadeRestService.reply was called but there is no web message to reply to) is raised.
Re-implement the reply method on the JadeRestService subclass that is being used. When using manual testing processing, to avoid raising exception 11127, the reply method should not call inheritMethod.