GeeCON Prague 2014*
The moose likes Websphere and the fly likes Modifying web.xml after enterprise application is already deployed Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


JavaRanch » Java Forums » Products » Websphere
Bookmark "Modifying web.xml after enterprise application is already deployed" Watch "Modifying web.xml after enterprise application is already deployed" New topic
Author

Modifying web.xml after enterprise application is already deployed

Martin Lira
Ranch Hand

Joined: May 26, 2004
Posts: 97
Hi All,
I have an enterprise application (EAR file) that is deployed on a WAS 5.0. It consists of couple of web modules (WAR files). I made changes in some beans used in one of the web modules and added a new DataSource. Is there any way I can directly go and modify the web.xml for the web module and specify the resource references to the new DataSource directly rather than going through the process of redeploying?

Thanks,
Martin
Scott Duncan
Ranch Hand

Joined: Nov 01, 2002
Posts: 363
Yes. The web.xml file is cached in the WebSphere config/cells/cell_name/applications/ear_name/deployements/app_name/war_name/WEB-INF directory. You have to make the changes in both places (the cache and the app) and then restart the application.

Honestly, you are better of just doing an update.


No more rhymes! I mean it!<br /> <br />Does anybody want a peanut?
Martin Lira
Ranch Hand

Joined: May 26, 2004
Posts: 97
thanks for pointing that out William. But I found a work around. I am using the jndi name directly instead of the resource reference "java:comp/env/jdbc/ds". Is there any drawback of using this?


Thanks,
ML

[ August 30, 2004: Message edited by: Martin Lira ]
[ August 30, 2004: Message edited by: Martin Lira ]
Dminds Soln
Greenhorn

Joined: Jul 01, 2013
Posts: 1
Scott Duncan wrote:Yes. The web.xml file is cached in the WebSphere config/cells/cell_name/applications/ear_name/deployements/app_name/war_name/WEB-INF directory. You have to make the changes in both places (the cache and the app) and then restart the application.

Honestly, you are better of just doing an update.


Thanks for the hint...
 
GeeCON Prague 2014
 
subject: Modifying web.xml after enterprise application is already deployed