[V5.1.1 and later]Deprecated V5.1 features

This document summarizes deprecated features in V5.1. As they become available, links to additional information will be provided to help you migrate away from deprecated features.

IBM Deprecation policy

A deprecated class or interface is supported for at least two full product releases or three full years (whichever is longer) before being removed from the product entirely.

Deprecation list

The following tables summarize what is deprecated, by release and version. Use these tables to calculate the earliest release in which the item might be removed, according to the deprecation policy.

For more information on deprecated APIs, refer to the "Deprecated" section at IBM WebSphere Application ServerTM, Release 5 API Specification.

Each table represents on what release/version the deprecation took effect. Each table describes what is being deprecated, for example; features, APIs, scripting interfaces, tools, wizards, publicly exposed configuration data, naming identifiers, constants, etc., and, where possible, the recommended migration action IBM suggests.

This article consists of the following versions/releases:


Deprecated features in V5.1.1[V5.1.1 and later]

Installation and migration tools
No deprecated features.
Servers and clustering features
No deprecated features.
Application programming model and container support features
The Web services gateway customization API is deprecated.

Recommended migration action:

No action is required at this time. However, use of Java API for XML-based Remote Procedure Call (JAX-RPC) handlers is recommended over Web services gateway-specific interfaces, such as filters, where possible. The Web services gateway API will be replaced in a future release. For more information, see JAX-RPC handlers - An alternative to gateway filters.

Application services features
The following JDBC drivers are deprecated:

  • MS SQL Server 2000 Driver for JDBC

  • SequeLink JDBC driver for MS SQL Server

Recommended migration action:

If you are using either of these JDBC drivers and still want to use MS SQL Server as their database, you can switch to the Connect JDBC driver. You can purchase the Connect JDBC driver from DataDirect Technologies, or you can use the Connect JDBC driver shipped with WebSphere Application Server, which is free for use with WebSphere Application Server.

J2EE resource features
No deprecated features.
Security features
No deprecated features.
Environment features
No deprecated features.
System administration features
No deprecated features.
Performance features
No deprecated features.
Problem determination features
No deprecated features.



Deprecated features in V5.1

Installation and migration tools
The Application Assembly Tool (AAT) used for developing J2EE applications is being replaced by the Assembly Tool (ATk) component of the Application Server Toolkit (ASTk).

Recommended migration action:

Instead of running the Application Assembly Tool, users will install and run the Assembly Toolkit component of the Application Server Toolkit. ASTk is based on the eclipse framework. Upon starting the ASTk, the J2EE function is found by opening the J2EE Perspective.

JDOM (a Java representation of an XML document which provides an API for efficient reading, manipulating and writing documentation). The currently packaged version of JDOM in WebSphere Application Server will not be packaged in future releases of WebSphere.

Recommended migration action:

Go to JDOM and get the latest copy of JDOM and bundle it inside your application.

Note: Customers running WebSphere Studio Application Developer Integration Edition Version 4.1 applications will need to migrate them to WebSphere Studio Application Developer Integration Edition V5.0.

In future releases, IBM intends to remove the C++ Object Request Broker (ORB), the C++ library for IDL valuetypes and the WebSphere Application Server C++ security client. IBM will no longer ship or support the Common Object Request Broker Architecture (CORBA) C++ Developer Kit. The CORBA technology is a bridge for migration to a Java 2 Platform Enterprise Edition (J2EE) and WebSphere Application Server environment.

In addition to the preceding information, the CORBA C++ client feature will be removed from the Application Clients installation image in future releases.

Recommended migration action:

It is recommended that customers migrate to the Object Request Broker (ORB) service for Java technology that ships with WebSphere Application Server. However, there is no equivalent J2EE functionality for the C++ security client or the C++ Valuetype library. Customers that require such functionality must provide or develop their own. For information on the ORB service for Java technology, see Managing Object Request Brokers.

The deprecation of the CORBA C++ Developer Kit does not affect support for CORBA interoperability with vendor software for CORBA services. View the following links for additional information about interoperability:

IBM Cloudscape 5.1.x.

Recommended migration action:

No action is required at this time.

Servers and clustering features
IBM HTTP Server (IHS) 1.3.x.

Recommended migration action:

If you are using IHS 1.3.x with modules:

  • that are shipped as part of IHS 1.3.x packages, you do not need to take any action to migrate those modules.

  • supplied by a third party (including other IBM products), you need to obtain IHS/Apache 2 versions of these modules from the third party.

  • that have been customized or are in-house, you need to port these modules to the new IHS/Apache 2 API.

Application programming model and container support features
Bean Scripting Framework (BSF). JSP execution and debugging functionality is being deprecated in WebSphere Application Server version 5.1.

Recommended migration action:

If using the Javascript, Tcl, and Python languages, the functionality will need to be rearchitected. If using BSF scripting in your own custom applications, they will be unaffected. Custom scripts written for the WebSphere Application Server admin console will also be unaffected.

This functionality will continue to exist in WebSphere Application Server app server release 5.1, and succeeding releases, until version 6.0. If debugging JSPs you may have to restart the app server during Javascript debugging sessions.

Data access programming interfaces in com.ibm.websphere.rsadapter.

Relational resource adapter interface:

(com.ibm.websphere.rsadapter)

Methods have been deprecated in these types:

com.ibm.websphere.rsadapter.OracleDataStoreHelper
    public void doSpecialBLobWork(ResultSet rset, 
                InputStream[] data, String[] blobColumnNames)  
    public String assembleSqlString(String[] blobColumnNames, 
                  StringBuffer whereClause, String[] varValues, String tableName)

Recommended migration action:

These relational resource adapter deprecated methods do not impact the application.

Note: You will not need to implement these deprecated methods in their subclasses if you have the subclass of OracleDataStoreHelper class. Those deprecated methods will not be called by the WebSphere Application Server runtime.

Webcontainer API modifications:

Note: There are no declared deprecations. The only changes are caused because of a Java API that changed between 1.3 and 1.4.

The changed class is com.ibm.websphere.servlet.error.ServletErrorReport. The return signature for getStackTrace( ) is changed because java.lang.Throwable now defines the same method with a different return signature.

  • Old method signature 

    public String getStackTrace();  
// returns a String representation of the
exception stack

  • New method signature (JDK 1.4, WebSphere Application Server 5.1) 

    public StackTraceElement[] getStackTrace(); 
// returns an array of stack trace
elements

  • Replacement method (WebSphere Application Server 5.1) (a replacement method that carries on the old functionality has been provided): 

    public String getStackTraceAsString(); 
// returns a String representation
of the Exception Stack

Recommended migration action:

If you are using com.ibm.websphere.servlet.error.ServletErrorReport.getStackTrace( ) and expecting a return type of String, you need to change your application to use the replacement method.

Application services features
Data access binaries -- Common Connector Framework:

The following jar files will be deprecated in V5.1:

  • ccf.jar

  • ccf2.jar

  • recjava.jar

  • eablib.jar

Recommended migration action:

The J2EE Connector Architecture solution should be used instead of the Common Connector Framework.

For more information on the usage (tools and runtime) of the J2EE Connector Architecture see Data access from J2EE Connector Architecture applications.

Setting the XA partner log directory via the 'TRANLOG_ROOT' variable is deprecated in V5.1.

Recommended migration action:

The setting currently stored in the TRANLOG_ROOT variable (if any) will need to be added to the Transaction Service panel for any servers who wish to use the XA partner log. If the default location is to be used, then no action is required. The Transaction Service panel can be found on the Administrative Console by selecting Application Servers on the left, choosing the application server to be modified, and selecting Transaction Service on the panel that is displayed. The directory currently in TRANLOG_ROOT should be entered in the Logging Directory box on the panel.

J2EE resource features
No deprecated features.
Security features
Security programming interfaces:

  • The API is being deprecated for 

    com.ibm.websphere.security.auth.WSPrincipal.getCredential()

    Recommended migration action:

    Instead of getting the WSCredential from the principal, now use one of the following methods to get the Subject which contains the WSCredential:

    • The RunAs Subject is the Subject used for outbound requests.

    • The Caller subject is the Subject that represents the authenticated caller for the current request.

    • The methods to use to get the runAs and caller subjects are 

      com.ibm.websphere.security.auth.WSSubject.getRunAsSubject()
      and 

      com.ibm.websphere.security.auth.WSSubject.getCallerSubject()
      respectively.

  • The interface is being deprecated in 

    com.ibm.websphere.security.auth.WSSecurityContext

    Recommended migration action:

    Use JAAS for any authentication related functionality.

  • The exception is being deprecated in 

    com.ibm.websphere.security.auth.WSSecurityContextException

    Recommended migration action:

    Use JAAS for any authentication related functionality.

  • The class is being deprecated in 

    com.ibm.websphere.security.auth.WSSecurityContextResult

    Recommended migration action:

    Use JAAS for any authentication related functionality.

Environment features
No deprecated features.
System administration features
The following class is deprecated: 

com.ibm.websphere.rsadapter.DB2390DataStoreHelper

Recommended migration action:

If you currently use the DB2390DataStoreHelper class for the DB2 Legacy CLI-based provider when you are accessing data, you should now use the DB2DataStoreHelper class.

If you currently use the DB2390DataStoreHelper class for the DB2 Universal JDBC provider driver when you are accessing data, now use the DB2UniversalDataStoreHelper class.

Performance features
No deprecated features.
Problem determination features
No deprecated features.



Deprecated features in V5.0.2

Installation and migration tools
No deprecated features.
Servers and clustering features
No deprecated features.
Application programming model and container support features
Apache SOAP channel in Web services gateway.

Recommended migration action:

Gateway services should be deployed to the SOAP HTTP channel instead of the Apache SOAP channel. The Endpoint ( URL) of the service will be different for this channel and therefore client programs that are talking to the gateway will need to use the new service Endpoint.

Apache SOAP, WEBSJAVA.SOAP:

  • soap.jar,

  • wssoap.jar

Recommended migration action:

See Migrating Apache SOAP Web services to Web Services for J2EE for more information.

Application services features
Data access programming interfaces in com.ibm.websphere.rsadapter.

Relational resource adapter interface:

(com.ibm.websphere.rsadapter)

Methods have been deprecated in these types:

  • com.ibm.websphere.rsadapter.DataStoreHelper
    public int processSQL(java.lang.String.sqlString, int isolevel, 
               boolean addForUpdate, boolean addextendedForUpdateSyntax);
    public DataStoreAdatperException mapException(DataStoreAdapterException e);

  • com.ibm.websphere.rsadapter.GenericDataStoreHelper
    public int processSQL(java.lang.String.sqlString, int isolevel, 
               boolean addForUpdate, boolean addextendedForUpdateSyntax);
    public DataStoreAdatperException mapException(DataStoreAdapterException e);

  • com.ibm.websphere.rsadapter.WSCallHelper
    public static DataStoreHelper createDataStoreHelper(String dsClassName)

Recommended migration action:

These relational resource adapter deprecated methods do not impact the application.

Note: You will not need to implement these deprecated methods in their subclasses if you have the subclass of GenericDataStoreHelper. Those deprecated methods will not be called by the WebSphere Application Server runtime.

For com.ibm.websphere.rsadapter.WSCallHelper, please use the getDataStoreHelper(datasource) method to get a DataStoreHelper object.

J2EE resource features
No deprecated features.
Security features
No deprecated features.
Environment features
No deprecated features.
System administration features
The testConnection command in the AdminControl scripting object ($AdminControl TestConnection configId props) is deprecated. Running this command in WebSphere Application Server, Version 5.0.2 or later returns the following message: WASX7390E: Operation not supported - testConnection command with config id and properties arguments is not supported. Use testConnection command with config id argument only.

Recommended migration action:

As of WebSphere Application Server, Version 5.0.2 or later, the preferred way to test a data source connection is the testConnection command passing in the data source configuration ID as the only parameter.

The getPropertiesForDataSource command in the AdminControl scripting object ($AdminControl getPropertiesForDataSource configId) is deprecated. This command incorrectly assumes the availability of the configuration service when you run it in the connected mode. Running this command in WebSphere Application Server, V5.0.2 or later returns the following message: WASX7389E: Operation not supported - getPropertiesForDataSource command is not supported.

Recommended migration action:

There is no replacement for this command.

Performance features
No deprecated features.
Problem determination features
No deprecated features.



Deprecated features in V5.0.1

Installation and migration tools
No deprecated features.
Servers and clustering features
No deprecated features.
Application programming model and container support features
No deprecated features.
Application services features
Data access programming interfaces in com.ibm.websphere.rsadapter.

Relational resource adapter interface:

(com.ibm.websphere.rsadapter)

Methods have been deprecated in these types:

  • com.ibm.websphere.rsadapter.DataStoreHelper
public int processSQL(java.lang.String sqlString, int isolevel);

  • com.ibm.websphere.rsadapter.GenericDataStoreHelper
public int processSQL(java.lang.String sqlString, int isolevel);

  • com.ibm.websphere.rsadapter.DB2390DataStoreHelper 
public int processSQL(java.lang.String sqlString, int isolevel);

Recommended migration action:

These relational resource adapter deprecated methods do not impact the application.

Note: You will not need to implement these deprecated methods in their subclasses if you have the subclass of com.ibm.websphere.rsadapter.GenericDataStoreHelper. Those deprecated methods will not be called by the WebSphere Application Server runtime.

J2EE resource features
No deprecated features.
Security features
No deprecated features.
Environment features
No deprecated features.
System administration features
No deprecated features.
Performance features
No deprecated features.
Problem determination features
No deprecated features.



Deprecated features in V5.0

Installation and migration tools
No deprecated features.
Servers and clustering features
No deprecated features.
Application programming model and container support features
No deprecated features.
Application services features
The following three methods from com.ibm.websphere.appprofile.accessintent.AccessIntent are deprecated: 

public boolean getPessimisticUpdateHintWeakestLockAtLoad();

public boolean getPessimisticUpdateHintNoCollision();

public boolean getPessimisticUpdateHintExclusive();

This is a base api.

Recommended migration action:

Rather than using the three deprecated methods on the AccessIntent interface, developers should use the following method from the same interface:

public int getPessimisticUpdateLockHint();

The possible return values are defined on the AccessIntent interface: 

public final static int PESSIMISTIC_UPDATE_LOCK_HINT_NOCOLLISION = 1;

public final static int PESSIMISTIC_UPDATE_LOCK_HINT_WEAKEST_LOCK_AT_LOAD = 2;

public final static int PESSIMISTIC_UPDATE_LOCK_HINT_NONE = 3;

public final static intPESSIMISTIC_UPDATE_LOCK_HINT_EXCLUSIVE = 4;

Web application programming interfaces -- Various Version 5 methods in com.ibm.websphere.ServletErrorReport
J2EE resource features
No deprecated features.
Security features
No deprecated features.
Environment features
No deprecated features.
System administration features
No deprecated features.
Performance features
Performance Monitoring Infrastructure -- Various Version 5 public methods in:

  • com.ibm.websphere.pmi.stat.StatsUtil

    Recommended migration action:

    There is no replacement for StatsUtil.

  • com.ibm.websphere.pmi.PmiJmxTest

    Recommended migration action:

    Use PmiClient.findConfig().

  • com.ibm.websphere.pmi.client.PmiClient

    Recommended migration action:

    The getNLSValue (String key) is replaced by getNLSValue (String key, String moduleID).

Problem determination features
No deprecated features.