JAX-RS web services created in earlier versions of the product are affected by WebSphere Application Server v8.0 supporting Feature Pack for Web 2.0 v1.0.x and v1.1.0 coexistence. This results in Rational Application Developer supporting the four JAX-RS 1.1. library providers as well as the four deprecated JAX-RS 1.0.x library providers.
If you are migrating a project referencing the Feature Pack for Web 2.0 v1.0.x JAX-RS libraries into a newer version of Rational Application Developer, your project will only work if you still have Feature Pack for Web 2.0 v1.0.x installed. If you have migrated to Feature Pack for Web 2.0 v1.1, you will need to migrate your project to use the newer JAX-RS libraries. This can be done by right-clicking the project and selecting and selecting a new library type.
Exception thrown: com.ibm.etools.webservice.deploy.core.WebserviceXMLException: Compilation error in *.jar
Problem: An EAR file created and exported from the workspace fails to deploy on WebSphere® Application Server 6.1.x resulting in the following error: class file has wrong version 49.0, should be 48.0 Please remove or make sure it appears in the correct subdirectory of the classpath
Cause: When creating a project, the default JDK compiler is JDK 5.0. The WebSphere Application Server 6.1.x JDK level is 1.4. Java 1.4 creates class files labeled with version 48.0. Java 1.5 creates class files labeled with version 49.0. Java 1.4 cannot run class files labeled with version 49.0.
When migrating a client application with some policy set configuration from WebSphere Application Server 6.1.0.9 ( the version installed with Rational Application Developer v7.0.0.x) or older to an environment that uses a later WebSphere Application Server level (such as in WebSphere Application Server v7.5), the client side policy set binding configuration need to be updated. In WebSphere Application Server v6.1.0.9 and older, the tools generated a custom client binding configuration to compliment the Server Side Default Binding. When migrating this client application and its service to a more recent WebSphere Application Server level, you need to change to use the client side default binding as well.