Do you have a situation where the project deployment is normal and the system is not logged in?
Do you encounter boot, WebLogic prompt database connection timeout?
.....
All the problems will be in the face of this artifact file to naught!
<?xml version= ' 1.0 ' encoding= ' UTF-8 '? ><weblogic-web-app xmlns= "Http://www.bea.com/ns/weblogic/90" > <charset-params> <input-charset> <resource-path>/*</resource-path> <java-charset-name >utf-8</java-charset-name> </input-charset> </charset-params> <container-descriptor> <!--let WebLogic in conflict situations, default to the Lib under the Web application instead of the jar--and <prefer-web-inf-classes>true</under its own classpath Prefer-web-inf-classes> </container-descriptor></weblogic-web-app>
Above, all copies are saved as: Weblogic.xml to the Web. XML peer location, run absolute OK.
This article is from the "foam gold it experience and skills" blog, please be sure to keep this source http://zl0828.blog.51cto.com/2242565/1672002
"WebLogic dry" instantaneous operation of normal Weblogic.xml insider