12.3.1 Migration to alternative functionality
You might need to migrate the functionality used by Application Server version 9 and Developer version 9 to alternative functionality so that the functionality can operate in Application Server version 11 and Developer version 11. Check the following table, and migrate applications as needed. Functionality not included in the table is compatible with Application Server version 9 and Developer version 9.
Functionality |
Case in which migration is required |
Reference |
---|---|---|
Servlet |
If the application uses non-supported Servlet 3.0 APIs and the UnsupportedOperationException exception is expected to be thrown |
|
If the application uses the dynamic servlet definition API to invoke the addMapping method of ServletRegistration to map to the context root (URL pattern is /), but the mapping is not expected to be performed correctly |
||
CDI |
If the application uses CDI annotations, but CDI is not expected to operate without beans.xml being stored in the application archive |
|
If a library having a Portable Extension implementation class is added to the class path or stored in the application, but the Portable Extension is not expected to operate |
||
JAX-RS |
If the application was using the Cosminexus JAX-RS engine (if cjjaxrs.jar was added to the class path) |
|
If the application was using parameters unique to the Cosminexus JAX-RS engine |
||
If the application was using client APIs for RESTful Web Services unique to the Cosminexus JAX-RS engine |
||
JPA |
If the application was using parameters unique to the CJPA provider (User properties that start with cosminexus.jpa, or values specified in <property> tags in persistence.xml) |
|
If the application was using the persistence units or persistence context for container management.
|
||
If the application was using a database other than HiRDB for the persistence destination database |
||
JSF |
If the application was using JSF (if cjsf.jar was added to the class path) |