I developed a web application which calls the methods that are part of some third party jar file. I am able to run the application successfully without any issues in APACHE-TOMCAT web server. When the same web application created as a WAR file and deployed in the websphere application server, i am facing an exception (java.lang.NoSuchMethodError) when a method that is part of the third party jar file is called.
Can you give me any suggestions. What makes it go wrong in case of websphere application server?
Info provided in the WAS links are some best practices of making all the dependent jars for the webapp available in the WEB-INF/lib folder and making the web classloader policy as PARENT_LAST. This will make your app truly portable across different appservers as you are no longer depending on the runtime for your app-specific needs.
There is much to this. When you compile your classes in your dev environment using 3rd party jars, previously there was no way of mentioning your dependencies, i.e., 1.2 version of commons-logging.jar. Recently, folks came out with a way of doing this in the manifest file. I think you should then write some small script bundled with your app that tests for the required versions of dependent runtime and stops the app from even starting [much better than having a mis-behaving app]. [ June 01, 2008: Message edited by: Jayadev Pulaparty ]