Deprecated Version 5.1 features

This document summarizes deprecated features in Version 5.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 will be 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 WASTM, Release 5 API Specification.

Each table represents 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.0

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 (.war) 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
PMI -- Various Version 5 public methods in:

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...

Recommended migration action:

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

Note that 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 WAS 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.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:

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...

Recommended migration action:

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

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 WAS 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
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 WAS 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 that Customers running WSADIE V4.1 applications will need to migrate them to WSADIE V5.0.

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

Recommended migration action:

If you are using IHS 1.3.x with modules...

  • supplied by IBM, you do not need to take any action.

  • supplied by a third party, 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 WAS 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 WAS admin console will also be unaffected.

This functionality will continue to exist in WAS 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.

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 that There are no declared deprecations. The only changes are caused because of a Java API that changed between 1.3 and 1.4.

  • Old method signature 

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

  • New method signature (JDK 1.4, WAS 5.1)
    public StackTraceElement[] getStackTrace(); 
// returns an array of stack trace
elements

  • Replacement method (WAS 5.1) (a replacement method, which carries on the old functionality has been provided) 

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

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.

J2EE resource 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.

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.