Deprecated Version 5.1 items

This document summarizes deprecated features in Version 5.1. A deprecated class or interface is supported for at least two full product releases, or three full years (whichever is longer) before it is removed from the product.

Use the following information to calculate the earliest release when the item might be removed, according to the deprecation policy.

Installation and migration tools

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

Recommended migration action: Go to JDOM , obtain the latest copy of JDOM, and bundle it inside your application.

Note: Customers running WSADIE V4.1 applications need to migrate them to WSADIE V5.0.

Servers and clustering features

No deprecated features.

Application programming model and container support features

Bean Scripting Framework (BSF), which is a JSP execution and debugging function, is being deprecated in WebSphere Application Server Version 5.1.

Recommended migration action: If you use the JavaScript, Tcl, and Python languages, the functionality needs to be rearchitected. If you use BSF scripting in your own custom applications, they are unaffected. Custom scripts that are written for the WebSphere Application Server administrative console are also unaffected.

BSF functionality continues to exist in WebSphere Application Server Version 5.1 but will be fully deprecated in a future version of the application server, according to the deprecation policy. If you debug JSPs, you might have to restart the application 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 do not need to implement these deprecated methods in their subclasses if you have the subclass of OracleDataStoreHelper class. These deprecated methods are not called by the WebSphere Application Server run-time environment.
Web container API modifications:

Note: There are no declared deprecations. A Java API has changed between versions 1.3 and 1.4.
- Old method signature:
```
	public String getStackTrace();  
    // returns a String representation of the exception stack
	
```
- New method signature (J2SE^(TM) 1.4 in WebSphere Application Server Version 5.1):
```
	public StackTraceElement[] getStackTrace(); 
     // returns an array of stack trace elements
	 
```
- WebSphere Application Server Version 5.1 replacement method (a replacement method that supports the old functionality is provided):
```
	public String getStackTraceAsString(); 
     // returns a String representation of the Exception Stack
	 
```
  See Migrate Web applications for more information.
Web services gateway customization API
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.

Application services features

Data access binaries -- Common Connector Framework:

The following .jar files are deprecated in Version 5.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.

Security features

Security programming interfaces:
- The API is being deprecated for the following interface:
```
	com.ibm.websphere.security.auth.WSPrincipal.getCredential()
	
```
  Recommended migration action: Obtain the Subject that contains the WSCredential using one of the following methods:
  - 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 as follows:
```
com.ibm.websphere.security.auth.WSSubject.getRunAsSubject()
```
```
com.ibm.websphere.security.auth.WSSubject.getCallerSubject()
```
- The following interface is being deprecated:
```
	com.ibm.websphere.security.auth.WSSecurityContext
	
```
  Recommended migration action: Use JAAS for any authentication-related functionality.
- The following exception is being deprecated:
```
	com.ibm.websphere.security.auth.WSSecurityContextException
	
```
  Recommended migration action: Use JAAS for any authentication-related functionality.
- The following class is being deprecated:
```
	com.ibm.websphere.security.auth.WSSecurityContextResult
	
```
  Recommended migration action: Use JAAS for any authentication related functionality.

Environment features

No deprecated features.

System administration features

No deprecated features.

Performance features

No deprecated features.

Problem determination features

No deprecated features.