Jakarta Enterprise Beans 4.0 Persistent Timers · This feature enables the use of persistent timers in Jakarta Enterprise Beans.
Group: io.openliberty.features - All Dependencies
Jakarta Enterprise Beans 4.0 Home Interfaces · This feature enables the use of home interfaces in Jakarta Enterprise Beans.
Jakarta Enterprise Beans 4.0 · This feature enables support for Enterprise Beans written to the Jakarta Enterprise Beans 4.0 specification.
Jakarta Connectors 2.0 Inbound Security · This feature enables security inflow for resource adapters. This is the final release of this feature and is only compatible with Jakarta EE 9. For Jakarta EE 10, the same functionality is automatically enabled when the connectors and appSecurity features are enabled.
Jakarta Application Client Support for Server 2.0 · This feature enables the Liberty server to process Jakarta EE client modules and support remote Jakarta EE client containers.
MicroProfile Context Propagation 1.3 · This feature implements the MicroProfile Context Propagation 1.3 specification, which allows you to obtain class instances of CompletableFuture that are backed by an instance of ManagedExecutor and provides the ability to contextualize CompletableFuture actions.
MicroProfile 5.0 · This feature combines the Liberty features that support MicroProfile 5.0 for Cloud Native Java.
Password Utilities 1.0 · This feature enables support for obtaining the values of the user and password attributes of authData elements from an application, and also allows the use of the com.ibm.websphere.crypto.PasswordUtil class as an API.
JMS Message-Driven Beans 3.2 · This feature is superseded by mdb-3.2. Both features provide identical function; only the feature names are different. mdb-3.2 is the preferred feature name.
CouchDB Integration 1.0 · This feature has been stabilized. The strategic alternative to this feature is the cloudant-1.0 feature. This feature enables connections to CouchDB by providing a connector instance configured in the server configuration, which can be injected or accessed through JNDI. Applications use the ektorp client library to utilize the connector instance to work with CouchDB.
com.ibm.websphere.appserver.wimcore-1.0 · com.ibm.websphere.appserver.wimcore-1.0
com.ibm.websphere.appserver.servlet-servletSpi1.0 · com.ibm.websphere.appserver.servlet-servletSpi1.0
com.ibm.websphere.appserver.org.eclipse.microprofile.jwt-1.0 · com.ibm.websphere.appserver.org.eclipse.microprofile.jwt-1.0
com.ibm.websphere.appserver.managedBeansCore-1.0 · com.ibm.websphere.appserver.managedBeansCore-1.0
com.ibm.websphere.appserver.javax.mail-1.6 · com.ibm.websphere.appserver.javax.mail-1.6
com.ibm.websphere.appserver.javax.jsp-2.3 · com.ibm.websphere.appserver.javax.jsp-2.3
com.ibm.websphere.appserver.iioptransport-1.0 · com.ibm.websphere.appserver.iioptransport-1.0
com.ibm.websphere.appserver.iiopcommon-1.0 · com.ibm.websphere.appserver.iiopcommon-1.0
com.ibm.websphere.appserver.beanValidationCore-1.0 · com.ibm.websphere.appserver.beanValidationCore-1.0
com.ibm.websphere.appserver.authData-1.0 · com.ibm.websphere.appserver.authData-1.0
com.ibm.websphere.appclient.appClient-1.0 · com.ibm.websphere.appclient.appClient-1.0
Cloudant Integration 1.0 · This feature enables connections to Cloudant databases by providing a connector instance that's configured in the server configuration and can be injected or accessed through Java Naming and Directory Interface (JNDI). Applications use the Cloudant client library to access the connector instance.
OMG CORBA APIs and RMI-IIOP API · OMG CORBA APIs and RMI-IIOP API
OMG CORBA APIs and RMI-IIOP API · OMG CORBA APIs and RMI-IIOP API