WLS Initializes On ServletContext per WebService deployed in WAR, increasing deployment time
(Doc ID 2606132.1)
Last updated on OCTOBER 12, 2022
Applies to:
Oracle WebLogic Server - Version 12.2.1.2.0 and laterInformation in this document applies to any platform.
Symptoms
Weblogic initializes on ServletContext per WebService deployed in WAR, increasing deployment time.
For each SOAP based web service deployed in an application, weblogic creates a dedicated Servlet Context.
There is only one web.xml file per deployment.
What implications does this have?
- (a) We can specify one and only one context-root for that deployment but weblogic creates multiple context roots for the application
- (b) When we specify a servlet context filter we specify it for the application context - weblogic will have to create multiple servlet filters, one per artificial context root created per web service plus one for the actual real HTTP context-root specified in the web.xml.
- (c) A user might include in his WAR deployment libraries, like for example Mojarra, that listen to the creation of a Servlet request context to bind there.
- (b) When we specify a servlet context filter we specify it for the application context - weblogic will have to create multiple servlet filters, one per artificial context root created per web service plus one for the actual real HTTP context-root specified in the web.xml.
- (c) A user might include in his WAR deployment libraries, like for example Mojarra, that listen to the creation of a Servlet request context to bind there.
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |