Labels

.net (1) *nix (1) administration (1) Android (2) Axis2 (2) best practice (5) big-data (1) business-analysis (1) code re-use (1) continuous-integration (1) Cordova-PhoneGap (1) database (2) defect (1) design (3) Eclipse (7) education (1) groovy (2) https (2) Hudson (4) Java (1) JAX-RS (2) Jersey (3) Jetty (1) localization (1) m2eclipse (2) MapForce (1) Maven (12) MySQL (1) Nexus (4) notes (4) OO (1) Oracle (4) performance (1) Perl (1) PL/SQL (1) podcast (1) PostgreSQL (1) requirement (1) scripting (1) serialization (1) shell (1) SoapUI (1) SQL (1) SSH (2) stored procedure (1) STS (2) Subclipse (1) Subversion (3) TOAD (3) Tomcat (4) UML (2) unit-testing (2) WAMP (1) WAS (3) Windows (3) WP8 (2) WTP (2) XML (4) XSLT (1)

Thursday, January 22, 2015

Why won't changes to web.xml in deployment directory take effect in WebSphere?

Normally when a web application is deployed to WebSphere, the "exploded" .EAR file resides in a directory similar to

C:\Programs\IBM\WebSphere\AppServer\profiles\AppSrv01\installedApps\<your computer name here>Node01Cell\<EAR file name here>\<WAR file name here>

Most changes to files underneath this directory structure are reflected in the application after the web application is re-started.  However, making changes to web.xml here will not have any effect.  Instead, WebSphere stores a copy of web.xml in

C:\Programs\IBM\WebSphere\AppServer\profiles\AppSrv01\config\cells\<your computer name here>Node01Cell\applications\<EAR file name here>\deployments\<context root here>\<WAR file name here>\WEB-INF\web.xml

that it actually heeds.  Misleading, eh?
Posted by at
Labels:

No comments:

Post a Comment

Subscribe to: Post Comments (Atom)