Superseded features

If we are migrating the configuration from an earlier release of WAS, you should be aware of the various features that have been superseded in this release.

Stating that a feature is superseded indicates that a new feature or combination of features might provide an advantage over using the superseded feature. For example, new features might be used in place of the superseded feature in order to reduce the server footprint by excluding content that might not be necessary. The new feature or features might not completely replace the function of the superseded feature; therefore, you must consider the specific needs before deciding whether to change the configuration. Superseded features remain supported and valid for use in the configuration; the superseded label simply provides an indication that you might be able to improve the configuration.

Features superseded in v8.5.5

superseded in v8.5.5. This table describes the

Category	Superseded Feature	Superseding Feature or Features
Liberty profile security	appSecurity-1.0	appSecurity-2.0 This version of the appSecurity feature secures only applications that are based explicitly on the presence of other features. If the servlet-3.0 feature is present with the appSecurity-2.0 feature, web applications are secured. If the servlet-3.0 feature is not present, web applications are not secured. If the ejblite-3.1 feature is present with the appSecurity-2.0 feature, EJB applications are secured. If the ejblite-3.1 feature is not present, EJB applications are not secured.

Deprecated, stabilized, superseded, and removed features

Deprecated features

Stabilized features

Removed features