WAS v8.5 > New features > What has changed in this releaseTransitioning notes for development topics
When you upgrade the application server to a newer version, be aware of the following settings that you might want to change.
- Configure JavaServer Faces implementation
The Application Server JSF engine determines if the Sun Reference Implementation (RI) 1.2 or Apache MyFaces 2.0 is used from the Application Server run time. If either is used, the correct listener class is registered with the web container. We do not need to add the com.sun.faces.ConfigureListener or the org.apache.myfaces.StartupConfigureListener to your web.xml file.
- Configure the SCA JMS binding
Differences between the OSOA and OASIS JMS binding specifications might affect migration of applications from OSOA to OASIS. Some commonly encountered differences include:
- The validation schemas used for the OASIS applications are defined by the OASIS SCA specification. The OASIS binding schema definition mandates that binding elements appear in the exact order as defined in the schema. For OSOA applications, element order does not affect validation so, when migrating applications from OSOA, ensure the binding elements are in the order specified by the OASIS binding schema.
- For the <destination>, <connectionFactory>, and <activationSpec> elements, the name attribute is jndiName in OASIS.
- In OASIS composites, callback references must specify a destination element. The specified destination is used only if the destination cannot be determined from the scaCallbackDestination or JMSReplyTo properties of the service request message. In OSOA composites, callback references can omit the destination element if it is known that one of the properties is always set.
For information on other differences, consult the OASIS specification for additional information about specific elements.
- Migration of JPA applications and bean validation
The Bean Validation API and implementation are included in the v8.x product. To deploy the feature pack applications on v8.x, be aware of the following changes in configuration and runtime behaviors:
- In v7.0, the system property, com.ibm.websphere.validation.api.jar.path, is used to direct the feature pack run time to locate the Bean Validation API JAR file. In v8.x, the Bean Validation API JAR file is built into the product installation, therefore, this system property is ignored. However, the bean validation provider can still be overridden in v7 and v8.x when packaged in application or shared libraries. The third bullet describes this usage scenario.
- The bean validation implementation in WebSphere Application Server is automatically the effective default bean validation provider.
- If standard bean validation features are used by the JPA application, the com.ibm.websphere.validation.api.jar.path system property, and user-supplied bean validation provider can be removed from application deployment.
- If non-specification compliant or provider-specific features are used by an application, the bean validation provider that supports the required features must be packaged, configured, and deployed as a typical, third-party service provider in the user application, the application shared library, and the server associated shared library. Read more about shared library usage in applications for more information.
- Migration scenario for the getHeaderNames method
To ensure the most successful migration, the return type of the StoredResponse getHeaderNames method was changed to com.ibm.websphere.servlet.response.CollectionEnumerationHybrid<String>. This type implements both Collection<String> and Enumeration.
- Runtime considerations for SIP application developers
When a SIP application sends a request to a SIP URI over Transport Layer Security (TLS) in version 6.1, the request URI scheme changes from "sip" to "sips." In the current version, the scheme does not change. We can reverse the new behavior by changing the application code. With a "sips" URI, the behavior remains the same after upgrading from version 6.1 to 7.0 or above. See the information center topic Premigration considerations for more information.