Bug 1026813

Summary: [Doc Bug Fix] Describe implementation details of behaviour of servlet startup init method with exception
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Petr Sakař <psakar>
Component: DocumentationAssignee: vthemeli
Status: CLOSED DEFERRED QA Contact: Russell Dickenson <rdickens>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.2.0CC: anrobert, dmichael, eap-docs, jhradile, rhatlapa, smumford
Target Milestone: ---Keywords: Documentation, FutureFeature, Triaged
Target Release: EAP 6.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Known Issue
Doc Text:
The behaviour of the server when exceptions are thrown by servlets in their `init()` method or by `ServletContextListener.contextInitialized` is not defined by the Servlet specification and the JBoss EAP Developer Guide does not provide an explanation of JBoss EAP 6 behaves in this situation. The behaviour of JBoss EAP 6 in these situations can be summarized as follows: * If an exception is thrown by the servlet `init()` method, then the application will still be deployed but the servlet will not be available. * If an exception is thrown by `ServletContextListener.contextInitialized` then the deployment will fail. A future version of the JBoss EAP Developer Guide will provide more details.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2015-10-08 21:48:35 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Petr Sakař 2013-11-05 13:39:13 UTC 
Documentation does not describe how server behaves in case of deployment of web application with servlet with init method loaded on startup which throws exception. The behaviour in such situation is not defined by servlet specification and is left up to implementation.

In case od jboss the web application is successfully deployed but the servlet is unavailable.
OTOH exception in ServletContextListener.contextInitialized causes deployment to fail.