This rule flags references to
javax.ws.rs
packages.
If you are migrating to Java EE 7 but are not changing your JPA implementation level, you will need to configure the server to use the non-default implementation.
If you are using the binary application scanner, this rule is included when the target Java EE level is version 7. The rule advises you of any required server configuration to use the non-default implementation for JAX-RS.
WebSphere Application Server traditional V9.0 is Java EE 7 certified which includes JAX-RS 2.0 by default. If you are migrating to WebSphere Application Server traditional V9.0, you can configure your server to use the JAX-RS 1.1 implementation to minimize the migration impact on your application. For information on configuring WebSphere Application Server traditional, see Coexistence of JAX-RS 2.0 with JAX-RS 1.1. If you would like to migrate to JAX-RS 2.0 instead of staying on JAX-RS 1.1, the automated fix will change this.
Note: a WebSphere server can only have one default JAX-RS provider. If you are deploying multiple applications to the same server, they must all be compatible with JAX-RS 1.1. Run the application migration tools against all your applications to discover if any of your applications must upgrade to JAX-RS 2.0.
In Liberty, to use a combination of Java EE 6 and Java EE 7
technologies, all features must be configured individually.
The javaee-7.0 feature cannot be used in this case.
For more information, see
Supported Java EE 6 and 7 feature combinations.