Group: OpenLiberty Features

Sort by:Popular▼

✓Popular✓Newest

This feature enables support for HTTP Servlets written to the Java Servlet 3.1 specification. You can package servlets in Java EE specified WAR or EAR files. If servlet security is required, you should also configure an appSecurity feature. Without a security feature, any security constraints for the application are ignored.

com.ibm.websphere.appserver.eeCompatible-9.0

io.openliberty.mpCompatible-0.0

com.ibm.websphere.appserver.eeCompatible-10.0

com.ibm.websphere.appserver.classloading-1.0

com.ibm.websphere.appserver.containerServices-1.0

Jakarta Transactions 2.0

com.ibm.websphere.appserver.eeCompatible-6.0

com.ibm.websphere.appserver.transaction-1.2

This feature enables the use of Java Naming and Directory Interface (JNDI) to access server configured resources such as DataSources or JMS Connection Factories. It also allows access to Java primitives configured in the server as a jndiEntry.

This feature enables support for HTTP Servlets written to the Jakarta Servlet 5.0 specification. You can package servlets in Jakarta EE specified WAR or EAR files. If servlet security is required, you should also configure an appSecurity feature. Without a security feature, any security constraints for the application are ignored.

com.ibm.websphere.appserver.eeCompatible-7.0

io.openliberty.servlet.api-3.0

com.ibm.websphere.appserver.transaction-1.1

This feature enables support for securing the server runtime environment and applications; it includes a basic user registry. This feature supersedes appSecurity-1.0 and does not include servlet-3.0 or support for the LDAP user registry. To secure web applications, add the servlet-3.0 feature. To secure EJB applications, add the ejbLite-3.1 feature. To use LDAP, add the ldapRegistry-3.0 feature. When you add the appSecurity-2.0 feature to your server, you need to configure a user registry, such as the basic ...

io.openliberty.servlet.internal-3.1

OSGi Application

This feature enables support for HTTP Servlets written to the Java Servlet 4.0 specification. You can package servlets in Java EE specified WAR or EAR files. If servlet security is required, you should also configure an appSecurity feature. Without a security feature, any security constraints for the application are ignored.

com.ibm.websphere.appserver.eeCompatible-8.0

This feature enables support for HTTP Servlets written to the Jakarta Servlet 6.0 specification. You can package servlets in Jakarta EE specified WAR or EAR files. If servlet security is required, you should also configure an appSecurity feature. Without a security feature, any security constraints for the application are ignored.