Class 'MyEventSource' looks like designed for extension (can be subclassed), but the method 'onOpen' does not have javadoc that explains how to do that safely. If class is not designed for extension consider making the class 'MyEventSource' final or making the method 'onOpen' static/final/abstract/empty, or adding allowed annotation for the method.
Class 'MyEventSource' looks like designed for extension (can be subclassed), but the method 'onClose' does not have javadoc that explains how to do that safely. If class is not designed for extension consider making the class 'MyEventSource' final or making the method 'onClose' static/final/abstract/empty, or adding allowed annotation for the method.
Class 'MyEventSourceServlet' looks like designed for extension (can be subclassed), but the method 'newEventSource' does not have javadoc that explains how to do that safely. If class is not designed for extension consider making the class 'MyEventSourceServlet' final or making the method 'newEventSource' static/final/abstract/empty, or adding allowed annotation for the method.
Class 'Service' looks like designed for extension (can be subclassed), but the method 'createOrder' does not have javadoc that explains how to do that safely. If class is not designed for extension consider making the class 'Service' final or making the method 'createOrder' static/final/abstract/empty, or adding allowed annotation for the method.
Class 'Service' looks like designed for extension (can be subclassed), but the method 'sendOrder' does not have javadoc that explains how to do that safely. If class is not designed for extension consider making the class 'Service' final or making the method 'sendOrder' static/final/abstract/empty, or adding allowed annotation for the method.
Class 'Service' looks like designed for extension (can be subclassed), but the method 'assignToCourier' does not have javadoc that explains how to do that safely. If class is not designed for extension consider making the class 'Service' final or making the method 'assignToCourier' static/final/abstract/empty, or adding allowed annotation for the method.
Class 'Service' looks like designed for extension (can be subclassed), but the method 'pickedUpByCourier' does not have javadoc that explains how to do that safely. If class is not designed for extension consider making the class 'Service' final or making the method 'pickedUpByCourier' static/final/abstract/empty, or adding allowed annotation for the method.
Class 'Service' looks like designed for extension (can be subclassed), but the method 'arrivedDepot' does not have javadoc that explains how to do that safely. If class is not designed for extension consider making the class 'Service' final or making the method 'arrivedDepot' static/final/abstract/empty, or adding allowed annotation for the method.
Class 'Service' looks like designed for extension (can be subclassed), but the method 'arrivedFinalDepot' does not have javadoc that explains how to do that safely. If class is not designed for extension consider making the class 'Service' final or making the method 'arrivedFinalDepot' static/final/abstract/empty, or adding allowed annotation for the method.
Class 'Service' looks like designed for extension (can be subclassed), but the method 'delivering' does not have javadoc that explains how to do that safely. If class is not designed for extension consider making the class 'Service' final or making the method 'delivering' static/final/abstract/empty, or adding allowed annotation for the method.
Class 'Service' looks like designed for extension (can be subclassed), but the method 'delivered' does not have javadoc that explains how to do that safely. If class is not designed for extension consider making the class 'Service' final or making the method 'delivered' static/final/abstract/empty, or adding allowed annotation for the method.
Class 'Service' looks like designed for extension (can be subclassed), but the method 'deliveryFailed' does not have javadoc that explains how to do that safely. If class is not designed for extension consider making the class 'Service' final or making the method 'deliveryFailed' static/final/abstract/empty, or adding allowed annotation for the method.
Class 'Service' looks like designed for extension (can be subclassed), but the method 'deliverAgain' does not have javadoc that explains how to do that safely. If class is not designed for extension consider making the class 'Service' final or making the method 'deliverAgain' static/final/abstract/empty, or adding allowed annotation for the method.
Class 'Service' looks like designed for extension (can be subclassed), but the method 'getOrdersReadyForDelivery' does not have javadoc that explains how to do that safely. If class is not designed for extension consider making the class 'Service' final or making the method 'getOrdersReadyForDelivery' static/final/abstract/empty, or adding allowed annotation for the method.
Class 'Service' looks like designed for extension (can be subclassed), but the method 'getOrderStatus' does not have javadoc that explains how to do that safely. If class is not designed for extension consider making the class 'Service' final or making the method 'getOrderStatus' static/final/abstract/empty, or adding allowed annotation for the method.
Class 'ContextListener' looks like designed for extension (can be subclassed), but the method 'contextInitialized' does not have javadoc that explains how to do that safely. If class is not designed for extension consider making the class 'ContextListener' final or making the method 'contextInitialized' static/final/abstract/empty, or adding allowed annotation for the method.
Class 'ContextListener' looks like designed for extension (can be subclassed), but the method 'contextDestroyed' does not have javadoc that explains how to do that safely. If class is not designed for extension consider making the class 'ContextListener' final or making the method 'contextDestroyed' static/final/abstract/empty, or adding allowed annotation for the method.
