2 Deprecated and Removed Functionality

These sections describe deprecated functionality, removed functionality, and changed defaults in Oracle WebLogic Server 26 (26.1.0.0.0).

Deprecated Functionality in Oracle WebLogic Server 26 (26.1.0.0.0)

The following functionality and components have been deprecated in WebLogic Server 26 (26.1.0.0.0).

For the functionality and components deprecated in WebLogic Server 15c (15.1.1.0.0), see Deprecated Functionality in Oracle WebLogic Server 15c (15.1.1.0.0) in What's New in Oracle WebLogic Server.

XA Transactions Without Transaction TLog Write

XA transactions without Transaction TLog write are deprecated. Existing domains that rely on XA transactions without Transaction TLog write should plan to use XA transactions with Transaction TLog write enabled.

FastSwap

FastSwap is deprecated in Oracle WebLogic Server 26 (26.1.0.0.0).

FastSwap enables development-time redefinition of Java classes in supported exploded applications without redeploying the application.

Applications and development workflows that rely on FastSwap should plan to use standard application or module redeployment to apply class changes.

Removed Functionality and Components

The following functionality is removed from Oracle WebLogic Server 26 (26.1.0.0.0). Use the replacement APIs described in this section.

Legacy REST Management APIs

The legacy REST Management APIs under /management/wls and /management/tenant-monitoring are removed. Use the WebLogic Server REST Management APIs under /management/weblogic.

Changed Defaults and Access Restrictions

The following defaults and access restrictions changed in WebLogic Server 26 (26.1.0.0.0):

• JMS .NET clients are disabled by default. To continue using JMS .NET clients, explicitly enable SecurityConfigurationMBean.JMSDotNetClientEnabled and restart the server.
• Anonymous JMS .NET client access is no longer a special exception. It is governed by the server-level remote anonymous T3 policy. Anonymous access requires both the server-level RemoteAnonymousRMIT3Enabled policy and the domain-level SecurityConfigurationMBean.RemoteAnonymousJNDIEnabled policy to permit it. Otherwise, configure JMS .NET clients with credentials.
• JMS .NET client JNDI use is restricted to the WebLogic JMS operations required by the JMS .NET client. The server-side proxy uses a local WebLogic initial context and excludes client-supplied naming and transport settings, including Context.INITIAL_CONTEXT_FACTORY and Context.PROVIDER_URL. Lookups are restricted to supported local WebLogic JMS connection factories and destinations; external URL names and unsupported indirect bindings are rejected.
• IIOP is disabled by default. WebLogic Server 26.1.0.0.0 provides the domain-level SecurityConfigurationMBean.IIOPEnabled switch to enable or disable IIOP by default for servers and server templates in the domain. The server-level IIOPEnabled setting is derived from the domain-level default unless explicitly overridden at the server level.