We now support Java 8!

Not only that but some of the cool Java EE 7 features that you’ll have seen in recent betas are now available in WebSphere Application Server Liberty Profile V8.5.5.

So what are the shiny new Liberty features?

Get them now! Give feedback on dWAnswers

SPNEGO 1.0 Single sign-on for HTTP requests using Simple and Protected GSS-API Negotiation Mechanism (SPNEGO) web authentication. Enables users to log in to the Microsoft Domain controller once using their Windows workstations and access protected applications on Liberty servers without getting prompted again.

Single sign-on for HTTP requests using Simple and Protected GSS-API Negotiation Mechanism (SPNEGO) web authentication. OSGi App Integration 1.0 Allows OSGi applications in the same Liberty runtime to share their services with each other. The osgiAppIntegration-1.0 feature adds Liberty support for the Application-ImportService and Application-ExportService headers that are used for OSGi application integration in WAS full profile. The Liberty model differs from the full profile model only slightly, in that method parameters are passed by reference in Liberty, and by value in full profile. Liberty developers must add a ‘binding:=local’ directive to the relevant header entries for this reason.

Allows OSGi applications in the same Liberty runtime to share their services with each other. JDBC 4.1 Enables the use of JDBC 4.1 capability in JDBC drivers that comply with the JDBC 4.1 or higher specification. This includes the ability to: Abort connections in an asynchronous fashion using the Connection.abort(Executor) API. Establish a network timeout for connections using the Connection.setNetworkTimeout(Executor) API Set a default schema on a connection using the Connection.setSchema() API Automatically close a statement when dependent result sets are closed using the Statement.closeOnCompletion() API

Enables the use of JDBC 4.1 capability in JDBC drivers that comply with the JDBC 4.1 or higher specification. This includes the ability to: WebSocket 1.1 Provides a more robust way of handling generics when defining a WebSocket MessageHandler compared to WebSocket 1.0. If you’re using 1.0 and would like to change to 1.1, change the entry in your server.xml from <feature>websocket-1.0</feature> to <feature>websocket-1.1</feature> .

Provides a more robust way of handling generics when defining a WebSocket MessageHandler compared to WebSocket 1.0. If you’re using 1.0 and would like to change to 1.1, change the entry in your from to . JavaServer Pages 2.3 and Expression Language 3.0 The JSP 2.3 feature provides access to El3.0 functionality and enables exploitation of Servlet 3.1 features from a JSP. The EL 3.0 feature provides an implementation of the EL 3.0 specification and can be used as a stand-alone feature. Some of the new capabilities of EL 3.0 are: lambda expression, operations on collections, and static field and method references.

and The JSP 2.3 feature provides access to El3.0 functionality and enables exploitation of Servlet 3.1 features from a JSP. Admin Center The Admin Center has new support for monitoring and search. The monitoring capabilities are available for servers and applications. The available metrics include core JVM stats such as CPU utiliziation and heap size, as well as PMI metrics (available through the monitor-1.0 feature) which will enable metrics for servers as well as applications. The new search capability provides searching of applications, servers, clusters, and hosts by name, type, and state. Admin Center also supports display of administrative metadata, such as a resource’s owner, contacts and tags. The administrative metadata can be set via the new admin-metadata.xml file, which can be defined in the server’s configuration directory.

These technologies are now fully supported.

Get them now! Give feedback on dWAnswers