You might want to approach the subject from a slightly different angle.
WebSphere provides a runtime environment, and much of that is provided through jar files that IBM places on their runtime classpath. It's not really a detail a developer or WebSphere professional needs to know. I've been working with WebSphere for years, and I really don't think I've every bothered to look at all the jars they have provided.
However, a new WebSphere version corresponds to new versions of things such as the Servlet and JSP specification, maybe the EJB or Webservices specification, new portlet support on a portal server, etc. Indeed, many of these changes will come with new jar files, but the jar file itself isn't your concern. Your concern is that your new applications are compatible with the latest specifications provided by IBM, and that you're not using any deprecated or more importantly, non-supported classes or methods.
posted 11 years ago
Hi Cameron McKenzie, thanks for your reply,
I have come with other error while migrating the application in websphere from 5.1 to 6.1
I have done changes in code to remove the deprecated methods and apis.