Stabilized features

WAS v8.5 > Overview > Deprecated, stabilized, and removed features
Stabilized features

If you are migrating your configuration 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 thealternative function listed under Strategic Alternative. We 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 v8.5

Features stabilized in v8.5. This table describes the features that are stabilized in v8.5.

Category Stabilized Function Strategic Alternative
Application programming model and container support Use of the Common Base Event application-programming interface (API) for problem determination

Classes or Interfaces:

All classes and interfaces from org.eclipse.hyades.logging.* packages

Methods:

Use of CommonBaseEvent or CommonBaseEventLogRecord as a message parm in the following WsJDK14Logger methods:

public void trace(Object message)
public void trace(Object message, Throwable t)
public void debug(Object message)
public void debug(Object message, Throwable t)
public void info(Object message)
public void info(Object message, Throwable t)
public void warn(Object message)
public void warn(Object message, Throwable t)
public void error(Object message)
public void error(Object message, Throwable t)
public void fatal(Object message)
public void fatal(Object message, Throwable t)

Other:

Use of the eventfactory Logger.properties logger extension

CBE-XML-1.0.1 output format for showlog
CBE-1.0.1 output format for HPEL logviewer

Use of the custom property name="com.ibm.ws.logging.zOS.errorLog.format" and value "CBE-XML-1.0.1"

Use of the showlog command on z/OS

None

Features stabilized in v8.0

Features stabilized in v8.0. This table describes the features that are stabilized in v8.0.

Category Stabilized Function Strategic Alternative
Application programming model and container support ActiveX to EJB Bridge Do not use Active X to access EJB.
WASs V4 Data sources and ConnectionManager Use the WASs Data sources (non-V4) and ConnectionManager.
Use of CommonBaseEventLogRecord for logging Use standard java.util.logging API for logging; and when needed, use HPEL log and trace facility's LogViewer command to convert log and trace messages into Common Base Event XML.
System administration WAS Reliability, Availability, and Serviceability (RAS) basic logging formats—System.out, System.err, trace.log, and activity.log Use the High Performance Extensible Logging (HPEL) log and trace facility to improve logging performance as well as to improve analysis and merging of logs.

Features stabilized in v7.0

Features stabilized in v7.0. This table describes the features that are stabilized in v7.0.

Category Stabilized Function Strategic Alternative
Application programming model and container support EJB entity beans: Container-Managed Persistence (CMP) 1.x and 2.x, and Bean-Managed Persistence (BMP) Use the JPA for new database and other persistence-related operations.
JAX-RPC
The Java Community Process (JCP) is limiting the focus for enhancements to the JAX-RPC runtime for building web services; therefore, WAS will follow suit and limit enhancements.
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:

Deprecated, stabilized, and removed features
Deprecated features
Removed features

+
Search Tips | Advanced Search

Category	Stabilized Function	Strategic Alternative
Application programming model and container support	ActiveX to EJB Bridge	Do not use Active X to access EJB.
	WASs V4 Data sources and ConnectionManager	Use the WASs Data sources (non-V4) and ConnectionManager.
	Use of CommonBaseEventLogRecord for logging	Use standard java.util.logging API for logging; and when needed, use HPEL log and trace facility's LogViewer command to convert log and trace messages into Common Base Event XML.
System administration	WAS Reliability, Availability, and Serviceability (RAS) basic logging formats—System.out, System.err, trace.log, and activity.log	Use the High Performance Extensible Logging (HPEL) log and trace facility to improve logging performance as well as to improve analysis and merging of logs.

Category	Stabilized Function	Strategic Alternative
Application programming model and container support	EJB entity beans: Container-Managed Persistence (CMP) 1.x and 2.x, and Bean-Managed Persistence (BMP)	Use the JPA for new database and other persistence-related operations.
Application programming model and container support	JAX-RPC The Java Community Process (JCP) is limiting the focus for enhancements to the JAX-RPC runtime for building web services; therefore, WAS will follow suit and limit enhancements.	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.