No Jeanne... neither of them has changed, and thats what stumps me !!!
I have just modified a single action class which was there already, and subsequent change was made in struts-config.xml as well. But the change is so small that it will not effect the entire app to break down. Also, I made sure I have't broken the struts-config with any bad XML construct [or just lets say that the XML is well formed]. Googling on this didnt help me at all.
Joined: Apr 26, 2007
Jeanne, I finally fixed it... Thought I would share it here so that if anyone else runs into this trouble, you could use this "know-how".
I had added another jar [strutstestcase.jar], which would help me unit test my struts action classes. This guy, infact was internally making use of the servlet-api.jar. Since I was using maven to build my project, this dependency was automatically injected.
I went ahead and added the "scope" to "test" for strutstestcase.jar, and also added an "exclude" block inside the same, to exclude servlet-api.jar...... A restart of the WAS app server, and my application started up like a charm....
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com
subject: Struts application deployment trouble in WAS 6.1