Back to bug 1026813
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Dana Mison | 2013-11-25 00:17:09 UTC | CC | dmison | |
| Dana Mison | 2013-11-26 02:31:26 UTC | Doc Text | The behaviour of the server when exceptions 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 a servlet's `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. |
|
| Dana Mison | 2013-11-26 02:32:45 UTC | Doc Text | The behaviour of the server when exceptions 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 a servlet's `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. | The behaviour of the server when exceptions 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. |
| Doc Type | Bug Fix | Known Issue | ||
| Dana Mison | 2013-11-26 02:33:19 UTC | Doc Text | The behaviour of the server when exceptions 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. | 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. |
| Tom WELLS | 2014-02-11 04:57:26 UTC | Keywords | Documentation, FutureFeature, Triaged | |
| CC | twells | |||
| Tom WELLS | 2014-05-15 05:31:34 UTC | Keywords | Triaged | |
| Tom WELLS | 2014-05-27 01:19:30 UTC | Assignee | rdickens | eap-docs |
| Dana Mison | 2014-05-27 01:28:54 UTC | CC | dmison | |
| John Skeoch | 2014-06-18 07:21:07 UTC | CC | nobody | |
| Tom WELLS | 2014-08-14 13:13:07 UTC | Component | doc-Development_Guide | Documentation |
| Scott Mumford | 2015-02-05 02:29:20 UTC | Keywords | Triaged | |
| Target Release | --- | EAP 6.4.0 | ||
| CC | smumford | |||
| Scott Mumford | 2015-02-06 03:27:00 UTC | Summary | Describe implementation details of behaviour of servlet startup init method with exception | [Doc Bug Fix] Describe implementation details of behaviour of servlet startup init method with exception |
| John Skeoch | 2015-05-18 01:31:21 UTC | CC | twells | lcarlon |
| lcarlon | 2015-05-19 10:16:57 UTC | CC | lcarlon | |
| David Michael | 2015-07-17 04:49:44 UTC | CC | dmichael | |
| Assignee | eap-docs | vthemeli | ||
| David Michael | 2015-07-27 11:08:49 UTC | CC | nobody | eap-docs |
| John Skeoch | 2016-02-10 01:35:05 UTC | Status | NEW | CLOSED |
| CC | anrobert | |||
| Resolution | --- | DEFERRED | ||
| Last Closed | 2015-10-08 17:48:35 UTC | |||
| CC | jhradile | |||
| Radim Hatlapatka | 2016-02-15 11:47:55 UTC | CC | rhatlapa |
Back to bug 1026813