Skip navigation.

Upgrading WebLogic Application Environments

  Previous Next vertical dots separating previous/next from contents/index/pdf Contents View as PDF   Get Adobe Reader

Compatibility with Previous Releases

This section describes important compatibility information that you should consider before upgrading to WebLogic Server 9.1.

Note: See also Compatibility Statement for BEA WebLogic Server 9.1 at

Compatibility considerations are provided in the following categories:


JMX 1.2 Implementation

As of WebLogic Server 9.0, WebLogic Server uses the Java Management Extensions (JMX) 1.2 implementation that is included in JDK 5.0. Prior to 9.0, WebLogic Server used its own JMX implementation based on the JMX 1.0 specification.

The JMX 1.2 reference implementation introduces serialization incompatibilities. As a result of these incompatibilities in the reference implementation, JMX clients created for WebLogic Server 9.0 or later cannot be used with WebLogic Server 8.1 or earlier. However, despite these incompatibilities, JMX clients created for WebLogic Server 8.1 can be used with 9.1 as follows:

BEA recommends that you update your JMX clients to be compliant with WebLogic Server 9.1. Prior to 9.0, WebLogic Server supported a typed API layer over its JMX layer. It was possible for your JMX application classes to import type-safe interfaces for WebLogic Server MBeans, retrieve a reference to the MBeans through the interface, and invoke the MBean methods directly.

As of 9.0, the MBeanHome interface is deprecated. Instead of using this API-like programming model, all JMX applications should use the standard JMX programming model, in which clients use the interface to discover MBeans, attributes, and attribute types at runtime. In this JMX model, clients interact indirectly with MBeans through the MBeanServerConnection interface.

If any of your classes import the type-safe interfaces (available under, BEA recommends that you update them to use the standard JMX programming model. For more information, see "Understanding WebLogic Server MBeans" in Developing Custom Management Utilities with JMX at


Dynamic Configuration Management

Configuration attributes are classified as dynamic or non-dynamic.

WebLogic Server 9.0 introduced a change management process to provide a secure, predictable means for applying configuration changes in a domain. A batch change mechanism changes the way dynamic changes are applied when they are mixed with non-dynamic changes. Specifically, when a configured server or system resource is affected by a change to a non-dynamic attribute, no other changes (even dynamic changes) will take effect, in current or future batches, until after the server or system resource is restarted. In this case, BEA recommends that you restart the entity as soon as possible after the batch change is completed to ensure the system is in a consistent state and to allow future changes to be accepted.

You should test your configuration scripts to determine whether a non-dynamic change has been applied, and if so, restart the server. To determine whether a change is non-dynamic and requires a server restart:

To determine which security attributes are dynamic or non-dynamic, see "Security Configuration MBeans" in Securing WebLogic Server at

For more information, see "Managing Configuration Changes" in Understanding Domain Configuration at


Modular Configuration and Deployment of JDBC Resources

As of WebLogic Server 9.0, the number of JDBC resource types was reduced to simplify JDBC configuration and to reduce the likelihood of configuration errors. Now, instead of configuring a JDBC connection pool and then configuring a data source or tx data source to point to the connection pool and bind to the JNDI tree, you can configure a data source that encompasses a connection pool. For more information about simplified JDBC resource configuration, see "Simplified JDBC Resource Configuration" in Configuring and Managing WebLogic JDBC at

The WebLogic Upgrade Wizard automatically converts JDBC data sources, connection pools, MultiPools, and data source factories to their new counterparts in WebLogic Server 9.1, as described in the following sections.

Note: Each upgraded JDBC module contains an internal properties section. WebLogic Server uses internal properties to manage the data sources for backward compatibility. Also, some legacy attributes are preserved as properties in the Properties attribute of the JDBC data source file. Do not manually edit any internal properties.

For information about deprecated JDBC features, methods, interfaces, and MBeans, see "Deprecated JDBC Features, Methods, Interfaces, and MBeans" in WebLogic Server and WebLogic Express Release Notes at

JDBC Data Sources and Connection Pools

The Upgrade Wizard converts legacy JDBC data source/connection pool pairs to two data source system resource modules, one for the data source and one for the connection pool:

During an upgrade, the Upgrade Wizard sets the GlobalTransactionsProtocol parameter for a data source based on the type of data source being converted (tx or non-tx) and the type of driver used in the related connection pool, as noted in the following table.

Table A-1 Parameter Settings for Global Transaction Protocol Parameter Setting 

Legacy Data Source Type

Driver Type

Emulate Two-Phase Commit


Tx Data Source




Tx Data Source



OnePhaseCommit (by default; not explicitly set)

Tx Data Source




Data Source




1. Depending on your environment, you may want to consider using the LoggingLastResource (LLR) transaction protocol in place of the EmulateTwoPhaseCommit protocol for transaction processing because of its performance benefits. For more information see "Understanding the Logging Last Resource Transaction Option" in Configuring and Managing WebLogic JDBC at



The Upgrade Wizard converts a MultiPool to a multi-data source, which is another instance of a data source object that provides load balancing and/or failover between data sources.

Data Source Factories

Data source factories are deprecated in this release and are included for backward compatibility only. No conversion of data source factories is required.


JDBC Debugging Enhancements

The JDBC subsystem uses the new system-wide WebLogic Diagnostic Service for centralized debugging access and logging.

See Using the WebLogic Diagnostic Framework Console Extension.


Modular Configuration and Deployment of JMS Resources

As of WebLogic Server 9.0, JMS configurations are stored as modules, defined by XML documents that conform to the new weblogic-jmsmd.xsd schema. With modular deployment of JMS resources, you can promote your application and the JMS configuration from one environment to another. For example, you can promote your application and the required JMS configuration from a testing environment to a production environment, without opening an EAR file and without extensive manual JMS re-configuration.

For more information, see:

The WebLogic Upgrade Wizard automatically converts pre-9.0 JMS resources to a JMS Interop module file named interop-jms.xml, which is copied to the domain's config\jms directory. For more information, see "JMS Interop Modules" in Configuring and Managing WebLogic JMS at

Please note the following JMS configuration changes:


JMS Message ID Format

As of WebLogic Server 9.0, the format of the JMS message ID has changed. BEA will continue to support the pre-9.0 format for existing consumers, producers, and servers. For example, existing JMS consumers may continue to view messages in the pre-9.0 format, even when received from a new JMS producer and JMS server.


Thread Management

BEA recommends using Work Manager concepts to manage threads, as execute queues are no longer the default method used as of WebLogic Server 9.0. You define the rules and constraints for your application by defining a Work Manager and applying it either globally to a WebLogic Server domain or specifically to an application component. For more information, see: "Using Work Managers to Optimize Scheduled Work" in Configuring WebLogic Server Environments at

In WebLogic Server 8.1, processing was performed in multiple execute queues. If you had been using execute queues to improve performance in 8.1, you may continue to use them after you upgrade your application domains. BEA provides a Use81StyleExecuteQueues flag that enables you to disable the self-tuning execute pool and provide backward compatibility for upgraded applications to continue to use user-defined execute queues. For information about enabling the backward compatibility flag, and configuring and monitoring execute queues, see "Using User-defined Execute Queues" in WebLogic Server Performance and Tuning at


JTA Transaction Log Migration

All JTA domain configuration options are persisted from the legacy configuration file. The only changes are at the server level. As of WebLogic Server 9.0, the Transaction Manager uses the default WebLogic persistent store to store transaction log records. During the upgrade, the Upgrade Wizard copies transaction log records to the default store. The transaction log file prefix from the existing server configuration is used only to locate the transaction log (.tlog) files during an upgrade; it is not preserved after the upgrade.

If the entire domain resides on a single machine, the Upgrade Wizard handles the upgrade (and copies transaction log records to the default store) for all Managed Servers during the initial domain upgrade. If Managed Servers reside on separate machines, you must upgrade each Managed Server individually, as described in Upgrade Your Application Environment.

Please note the following:

If you have put your transaction log files in network storage in preparation for Transaction Recovery Service migration, the log file location is not preserved after the upgrade. In this release, the WebLogic Server Transaction Manager uses the WebLogic default persistent store to store transaction log files. You can achieve the same result by moving the location of the WebLogic default persistent store to a network location. Note that you must manually copy the DAT file from the default location of the current default store to the new location of the default store.

If transactions will span multiple domains, you must configure your domain to enable inter-domain transactions. For more information, see "Configuring Domains for Inter-Domain Transactions" in Programming WebLogic JTA at



The following sections identify changes to security.

XACML Security Providers

As of 9.1, WebLogic Server includes two new security providers, the XACML Authorization provider and the XACML Role Mapping provider. Previous releases of WebLogic Server used an authorization provider and a role mapping provider based on a proprietary security policy language. These new XACML security providers support the eXtensible Access Control Markup Language (XACML) 2.0 standard from OASIS. These providers can import, export, persist, and execute policy expressed using all standard XACML 2.0 functions, attributes, and schema elements.

WebLogic domains created using WebLogic Server 9.1 include the new XACML providers by default. The new XACML providers are fully compatible with policies and roles created using the WebLogic Authorization provider (DefaultAuthorizer) and WebLogic Role Mapping provider (DefaultRoleMapper). Existing WebLogic domains that you upgrade to 9.1 will continue to use the authorization and role mapping providers currently specified, such as third-party partner providers or the original WebLogic Authorization and Role Mapping providers. If you wish, you can migrate existing domains from using WebLogic Server proprietary providers to the XACML providers, including performing bulk imports of existing policies. For more information, see Security for BEA WebLogic Server 9.1 at

New SAML V2 Providers

New versions of the SAML Credential Mapping provider and SAML Identity Assertion provider have been added in WebLogic Server 9.1. The SAML Credential Mapping V1 provider and SAML Identity Assertion V1 provider are deprecated; you should use the V2 versions of the SAML Credential Mapping and SAML Identity Assertion providers.

Although the version number of the providers has been incremented to V2, the new SAML security providers implement the SAML 1.1 standard, as did the V1 providers.

Security MBeans

The following table lists the changes to security MBeans as of WebLogic Server 9.0.

Table A-2 Changes to Security MBeans as of WebLogic Server 9.0 

Type of Security MBean


All security MBeans

In WebLogic Server 8.1, when you updated a security MBean attribute, the values were available to the security configuration and management hierarchy immediately, and to the security runtime hierarchy following a server reboot.

As of WebLogic Server 9.0, whether a security MBean attribute change is effective and available to the configuration, management, and runtime hierarchies immediately or upon server reboot is controlled by setting that attribute as dynamic or non-dynamic. For more information, see Dynamic Configuration Management.

RealmMBean, UserLockoutManagerMBean, and all security provider MBeans

  • The wls_getDisplay method is deprecated. In its place, you should use the new getName method. In addition, the following security methods have been removed:


  • The wlconfig and weblogic.Admin tools and pre-9.0 JMX security APIs can no longer be used to configure security MBeans. These utilities and APIs can still be used, however, to view and invoke methods on the security MBeans.

For security provider MBeans (only):

  • When adding or removing a security provider, you must reboot the server before any changes will take effect.

  • When modifying an existing security provider, if you modify any non-dynamic attributes, the server must be rebooted before any (that is, non-dynamic or dynamic) changes will take effect. For more information, see Dynamic Configuration Management.

All custom security provider MBeans

  • You can set an MBean attribute to be dynamic by setting Dynamic="true" for the attribute within the MDF file. For example:

Name = "Foo"
Type = "java.lang.String"
Dynamic = "true"
Description = "Specifies that this attribute is a dummy."


Password Encryption

To prevent unauthorized access to sensitive data such as passwords, some attributes in configuration MBeans are encrypted. The attributes persist their values in the domain configuration files as an encrypted string. For further security, the in-memory value is stored in the form of an encrypted byte array to help reduce the risk of the password being snooped from memory.

In pre-9.0 releases, you could edit the config.xml file to specify an encrypted attribute, such as a password, in clear-text or encrypted format. In this case, when booted, the WebLogic Server will encrypt the information the next time it writes to the file.

As of WebLogic Server 9.0, when operating in production mode, the password of an encrypted attribute must be encrypted in the configuration files. In development mode, the password of an encrypted attribute can be either encrypted or clear-text.

You can use the command-line utility to encrypt the passwords, as follows:


You are prompted to enter a password, and the command returns the encrypted version. Then, copy the encrypted password returned into the appropriate file.

This utility is not just used for passwords in the configuration files. It can also be used to encrypt passwords in descriptor files (for example, a JDBC or JMS descriptor) and in deployment plans. For more information, see "encrypt" in "Using the WebLogic Server Java Utilities" in WebLogic Server Command Reference at

Security for HTTP Requests

By default, when an instance of WebLogic Server 9.1 responds to an HTTP request, its HTTP response header does not include the WebLogic Server name and version number. This behavior is different from releases prior to WebLogic Server 9.0.

To have the name and version number included in the HTTP response header when responding to an HTTP request, enable the Send Server Header attribute for the WebLogic Server instance in the Administration Console. The attribute is located on the Server —>ServerName —> Protocols —>HTTP tab under the Advanced Options section. Note that enabling this feature may creates a security risk if a possible attacker knows about a vulnerability in the specified version of WebLogic Server.

For more information about ensuring security, see "Securing the WebLogic Security Service" in "Ensuring the Security of Your Production Environment" in Securing a Production Environment at

Secure Access to MBeanHome

In pre-9.0 releases of WebLogic Server, anonymous access to MBeanHome was enabled by default. With the security enhancements delivered with WebLogic Server 9.0, anonymous access to MBeanHome is no longer allowed.

Although doing so is not recommended, you can re-enable anonymous access by specifying the following flag when starting the server:

Message-Level Security in Web Services

As of WebLogic Server 9.0, message-level security in Web Services has been enhanced to use the standards-based Web Services Policy Framework (WS-Policy). WS-Policy provides a flexible and extensible grammar for expressing the capabilities, requirements, and general characteristics of entities in an XML Web Services-based system. For more information about WS-Policy, see "Using WS-Policy Files for Message-Level Security Configuration" in Programming Web Services for WebLogic Server at

In 8.1, the implementation was based on an OASIS implementation of the Web Services Security (WSS) standard. This implementation is supported for backward compatibility, but is deprecated as of 9.0. For more information, see


Web Services

WebLogic Server 8.1 Web Services can be run in 9.1, although the 8.1 Web Services run-time engine has been deprecated as of 9.0.

The WebLogic Server 6.1 or 7.0 Web Services need to be upgraded to 8.1 in order to run in 9.1. For more information, see "Upgrading WebLogic Web Services" in Programming WebLogic Web Services at

BEA strongly recommends that you upgrade, to 9.1, all of your 8.1 Web Services, including any 6.1 and 7.0 Web Services that have been upgraded to 8.1. For information about upgrading your existing 8.1 Web Services, see "Upgrading an 8.1 Web Service to 9.0" in Programming Web Services for WebLogic Server at

Note: See also Message-Level Security in Web Services.


Web Applications, JSPs, and Servlets

The following sections provide important compatibility information for Web applications, JSPs, and Servlets in WebLogic Server 9.0:

Deprecated and Obsolete Web Application Features

For a list of Web application features that are deprecated or are not supported as of WebLogic Server 9.0, see "Deprecated and Obsolete Web Application Features" in WebLogic Server and WebLogic Express Release Notes at

Support for JSP 2.0

JSP 2.0 is supported, as of WebLogic Server 9.0. For specific details, see Developing Web Applications, Servlets, and JSPs for WebLogic Server at

Please note the following changes to the JSP behavior:

Servlet Path Mapping

As of the Servlet 2.3 Specification from Sun Microsystems, which is downloadable at, the following syntax is used to define mappings:

These changes introduce a change in behavior with the following HttpServletRequest methods:

To better illustrate the change in behavior, consider a request /abc/def.html that resolves to ServletA:

To ensure that the path info returned is non-null, replace all occurrences of the / (forward slash) servlet mapping string with /*.


XML Implementation

Please note the following changes to XML support as of WebLogic Server 9.0:


XMLBeans and XQuery Implementation

As of 9.0, the XMLBean implementation in WebLogic Server has been moved from an internal BEA library (com.bea.xml) to the Apache open source project (org.apache.xmlbeans).

If you used XMLBeans in your WebLogic Server 8.1 applications, you must perform the following steps:

  1. Update the package name used by XMLBeans from com.bea.xml to org.apache.xmlbeans.
  2. Recompile your XMLBean schemas to update the schema metadata (.xsb) files and generated code.

As of 9.0, the XMLQuery (XQuery) implementation conforms to the following specifications:

In WebLogic Server 8.1, the XQuery implementation conformed to XQuery 1.0 and XPath 2.0 Functions and Operators—W3C Working Draft 16 August 2002, available from the W3C Web site at The 2002 XQuery implementation is deprecated as of 9.0.

In most cases, simple XQuery and XPath operations in pre-9.0 code will behave the same in 9.1. To ensure that the XQuery and XPath operations produce the expected results, you can review and/or update the existing XMLObject.selectPath() and XMLObject.execQuery() method calls using one of the following methods:

As of 9.0, the behavior of XMLCursor.moveXML() has changed. In 8.1, a cursor that was inside a moved fragment remained on the original document. As of 9.0, cursors move with fragments.


WebLogic Administration and Configuration Scripts

Due to changes with the MBean hierarchy, BEA does not guarantee that existing configuration and administration scripts (such as WLST, wlconfig, weblogic.Admin, Ant, and so on) will run in 9.1. BEA recommends that you update your scripts to take advantage of the new features provided as of WebLogic Server 9.0. For more information about new features and changes in the MBean hierarchy, see "What's New in WebLogic Server 9.0" in the WebLogic Server and WebLogic Express Release Notes at

For additional information about upgrading your application infrastructure and the scripting tools that have been deprecated, see Step 1: Upgrade Your Application Infrastructure.


Deprecated Deployment Features

For a list of application deployment features that are deprecated or no longer supported as of WebLogic Server 9.0, see "Deprecated and Unsupported Deployment Features" in WebLogic Server and WebLogic Express Release Notes at


Deployment Descriptor Validation and Conversion

This section describes changes in the use of deployment descriptors in a WebLogic Server environment, as of release 9.0:


Deprecated Startup and Shutdown Classes

As of 9.0, application-scoped startup and shutdown classes are deprecated in WebLogic Server, in favor of applications that respond to application lifecycle events. BEA recommends that you update your application environment to use the new 9.0 lifecycle events in place of application-scoped and domain-level startup and shutdown classes. For more information, see "Programming Application Lifecycle Events" in Developing Applications with WebLogic Server at


Administration Console Extension Architecture

The WebLogic Server Administration Console has been completely re-designed in the current release. The Administration Console is now built on the WebLogic Portal Framework, which makes it more open and more readily extensible.

The new architecture necessitates new procedures for extending the Administration Console. WebLogic Administration Console extensions built for prior releases of WebLogic Server will not function with the new Console infrastructure.

For more information about extending the Administration Console, see Extending the Administration Console at


Resource Adapters

The following table lists the configuration settings for resource adapters that are deprecated or no longer supported. For more information about new features and changes, see "New and Changed Features in This Release" in Programming WebLogic Resource Adapters at

Table A-3 Deprecated or Unsupported Resource Adapter Configuration Settings 

This element ...

As of WebLogic Server 9.0 ...

Link-Ref Mechanism

This element has been deprecated and replaced by the new J2EE libraries feature. For more information about J2EE libraries, see "Creating Shared J2EE Libraries and Optional Packages" in Developing Applications with WebLogic Server at

The Link-Ref mechanism is still supported in this release for resource adapters developed under the J2CA 1.0 Specification. For more information about using the Link-Ref mechanism with 1.0 resource adapters, see "(Deprecated) Configuring the Link-Ref Mechanism" in "Configuring the weblogic-ra.xml File" in Programming WebLogic Resource Adapters at


This element has been deprecated and replaced by <shrink-frequency-seconds>, which allows you to specify the shrink period in increments of seconds, instead of minutes.

The <shrink-frequency-seconds> element overrides the <shrink-period-minutes> element if both are set.


This element has been deprecated and is replaced by <inactive-connection-timeout-seconds>, which allows you to specify the connection timeout in increments of seconds.

The <inactive-connection-timeout-seconds> element overrides the <connection-maxidle-time> element if both are set.


This element is no longer supported; the security principal map is configured using the Administration Console.

You should remove the <security-principal-map> definition from the weblogic-ra.xml file. Otherwise, deployment of the resource adapter fails.


This element is no longer supported and is ignored during deployment.


This element is no longer supported and is ignored during deployment.




WLEC was deprecated in WebLogic Server 8.1. WLEC users should move applications to the WebLogic Tuxedo Connector, as described in WLEC to WebLogic Tuxedo Connector Migration Guide at


Backward Compatibility Flags

The following configuration flags are available to support backward compatibility when you upgrade a domain. By default, these flags are set to support backward compatibility, unless you disable them by selecting the Do not set backwards compatibility flags option during an upgrade, as described in Upgrading a Domain in Graphical Mode.

Table A-4 Backward Compatibility Flags 


Backward Compatibility Flag

For More Information


  • EnforceStrictURLPattern—Specifies whether the server should enforce strict adherance of URL patterns to the Servlet 2.4 specification. During an upgrade, this flag is set to false for backward compatibility.

  • WebAppFilesCaseInsensitive—Specifies whether the URL-pattern matching behavior is case-insensitive for security constraints, servlets, filters, virtual hosts, and so on, in the Webapp container and external security policies. During an upgrade, this flag is set to os, which sets URL-pattern matching as case-sensitive on all platforms except Windows, for compatibility with pre-9.0 releases. As of WebLogic Server 9.0, URL-pattern matching is strictly enforced across operating systems

SecurityConfigurationMBean at

Web Application

  • AllowAllRoles—Specifies that a wildcard (*) character can be used to set the role name to enable all users/roles in the realm to have access to the resource collection. As of WebLogic Server 9.0, if you specify the wildcard (*) character as the role name, all users/roles in the Web application will have access to the resource collection.

  • FilterDispatchedRequestsEnabled—Specifies whether to apply filters to dispatched requests. As of WebLogic Server 9.0, the new Dispatcher element makes this behavior explicit.

  • JSPCompilerBackwardsCompatible—Specifies whether to allow JSPs that do not comply with the JSP 2.0 specification.

  • ReloginEnabled—Specifies whether to allow users multiple attempts to log in to a Web page if the original credentials were not supported. As of WebLogic Server 9.0, the FORM/BASIC authentication behavior has been modified to return the 403 (FORBIDDEN) Web page.

  • RtexprvalueJspParamName—Specifies whether to allow run-time expression values for the JSP <param name> tag. As of WebLogic Server 9.0, the JSP Compiler no longer allows run-time expression values.

WebAppContainerMBean at



Deprecated and Removed APIs

This section summarizes APIs that have been deprecated or removed in WebLogic Server 9.0.

Note: If you want to rebuild the WebLogic Server 8.1 MedRec application in the 9.1 environment, you must replace references to the package with the new package name, weblogic.webservice.wsdl, in two Java files: medrec/src/common/web/com/bea/medrec/utils/ and medrec/src/clients/com/bea/medrec/webservices/swing/

The 8.1, 9.0, and 9.1 packages, and weblogic.webservice.wsdl, respectively, are not publicly available.

See also Web Services.

Deprecated APIs

For a list of deprecated APIs, see

Removed APIs

This section describes the APIs that have been removed in WebLogic Server 9.0, including:

Removed APIs, Deprecated in WebLogic Server 8.1

The following table provides a list of APIs that have been removed in WebLogic Server 9.0 and were deprecated in WebLogic Server 8.1.

Table A-5 Removed APIs—Deprecated in WebLogic Server 8.1 

Package Name

















HttpsURLConnection getDefaultHostnameVerifier()



boolean verify(java.lang.String, java.lang.String)

boolean verify(,



Removed APIs, Deprecated in WebLogic Server 7.0

The following table provides a list of APIs that have been removed in WebLogic Server 9.0 and were deprecated in WebLogic Server 7.0.

Table A-6 Removed APIs—Deprecated in WebLogic Server 7.0 

Package Name































CertAuthentication authenticate(java.lang.String,[], boolean)


CertAuthenticator authenticate(java.lang.String,[], boolean)


Security void receiveSecurityMessage(weblogic.rjvm.JVMID,


SecurityMessage void execute(weblogic.rjvm.JVMID)


Audit void certificateInvalid(java.lang.String, java.lang.Object,


Audit void rootCAInvalid(java.lang.String, java.lang.Object,


AuditProvider void certificateInvalid(java.lang.String, java.lang.Object,


AuditProvider void rootCAInvalid(java.lang.String, java.lang.Object,



































InvocableResource java.lang.String toString()




















TrustManager boolean certificateCallback([], int)




Removed APIs (Not Deprecated)

The following provides a list of APIs that have been removed in WebLogic Server 9.0, without being deprecated. Except where indicated, the APIs have been removed because the related functionality is no longer supported.

Note: In the following table, * (asterisk) represents a wildcard character.

Table A-7 Removed APIs (Not Deprecated) 

Package Name








CallbackDispatcher(weblogic.common.ClientCallback, boolean)




































java.lang.String getSharedCommoMBeanRepositoryIdentifier(
java.util.List getCommoMBeans(




WebLogicObjectName(java.lang.String, java.lang.String)


















void addNotification(weblogic.time.common.internal.TimerNotification)
java.lang.String getDispatchPolicy()
void removeNotification(weblogic.time.common.internal.TimerNotification)
void removeNotification(weblogic.time.common.internal.TimerNotification, boolean)
void run()
void setDispatchPolicy(java.lang.String)
void start(java.lang.ThreadGroup,java.lang.String,int)













void bind(java.lang.String, weblogic.rmi.Remote)
weblogic.rmi.Remote lookup(java.lang.String)
void rebind(java.lang.String, weblogic.rmi.Remote)
















void initialize(java.lang.String)
void main(java.lang.String[])
WebServiceResource WebServiceResource(, java.lang.String, java.lang.String[], java.lang.String[])




*verify(java.lang.String, java.lang.String)













ExecuteTask void execute(weblogic.kernel.ExecuteThread)



void main(java.lang.String)
void _setStrictChecking(boolean)

JSSEAdapter getSocketFactory()
void setSocketFactory(


void main(java.lang.String)





java.lang.String getName()

SecurityElementFactory createToken(java.lang.String, java.lang.String, javax.xml.namespace.QName)


String getPasswordType()

1. API functionality is supported by the java.util.logging.Handler class.



Skip navigation bar  Back to Top Previous Next