Stabilized features

If you are migrating from an earlier release of WebSphere® Application Server, you should be aware of the various features that have been stabilized in this release.

If a feature is listed here as stabilized, IBM® does not currently plan to deprecate or remove this capability in a subsequent release of the product; but future investment will be focused on the alternative function listed under "Strategic Alternative." You do not need to change any of your existing applications and scripts that use a stabilized function; but you should consider using the strategic alternative for new applications.

Features stabilized in Version 7.0

Table 1. Features stabilized in Version 7.0. This table describes the features that are stabilized in Version 7.0.
Category Stabilized Function Strategic Alternative
Application programming model and container support Enterprise JavaBeans (EJB) entity beans: Container-Managed Persistence (CMP) 1.x and 2.x, and Bean-Managed Persistence (BMP) Use the Java Persistence API (JPA) for new database and other persistence-related operations.
Java API for XML-based RPC (JAX-RPC)

The Java Community Process (JCP) is limiting the focus for enhancements to the JAX-RPC runtime for building Web services; therefore, WebSphere Application Server will follow suit and limit enhancements.

Java API for XML Web Services (JAX-WS) will become the strategic runtime on which any new enhancements will be focused. The focus to ensure interoperability for the subset of capabilities that map to the JAX-RPC and JAX-WS intersection will be maintained; but all new enhancements related to updating to support new standards will be only in the JAX-WS runtime.
System administration Application server administrative (wsadmin) scripting support for the Jacl language Use Jython syntax for any new wsadmin scripting.
J2EE resources Support for configuring and using message-driven beans (MDBs) through JMS listener ports Perform the following actions to use JMS activation specifications instead of listener ports:
  • Create a JMS activation specification to replace the listener port.
  • Modify the configuration of the application's Message Driven Bean listener bindings to use the activation specification instead of the listener port.
  • Because an JMS activation specification can be defined at a wider scope than a listener-port definition (which is restricted to server scope), you might be able to replace multiple listener-port definitions with a single activation specification.
  • Update any administrative scripts that define or administer listener ports to define or administer JMS activation specifications instead.
  • Update any administrative scripts that use the stop or start operations of the ListenerPort MBean to use the pause and resume operations on the Message Endpoint MBean instead.



Reference topic    

Terms of Use | Feedback

Last updated: Oct 21, 2010 5:30:17 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=was-nd-iseries&topic=rmig_stabfeat
File name: rmig_stabfeat.html