The latest Liberty profile beta contains stuff for both WebSphere® Application Server Liberty Profile and WebSphere Developer Tools (WDT).

Look out for more betas over the coming months…

Get it now! Give feedback on dWAnswers

What’s in the Liberty profile beta for August/September?

In the August/September beta, we’ve added:

  • JAX-RS 2.0 Initial support for JSR 339, Java API for RESTful Web Services, version 2.0. JAX-RS 2.0 provides portable APIs for developing, exposing, and accessing Web applications designed and implemented in compliance with principles of REST architectural style.
  • JMS 2.0 Two things:
    • Message delivery delay: User can specify a delivery delay value in milliseconds for each message that is sent. An application may specify the required delivery delay using the setDeliveryDelay method on the producer object. The setDeliveryDelay method sets the delivery delay for all messages sent using that producer.
    • Use of AutoCloseable: The Connection, Session, MessageProducer, MessageConsumer, and QueueBrowser interfaces have been modified to extend the java.lang.Autocloseable interface which is introduced in Java 7. This means that applications can create these objects using the Java 7 try-with-resources statement, without explicitly making a close() call when the objects are not required.
  • featureManager The featureManager install command introduces two new options: --downloadOnly and --from.
    • Use the --downloadOnly option to download the features from the Liberty Repository to a directory for offline use; for example:
      featureManager install portletserving-2.0 --downloadOnly=c:\temp\download --acceptLicense
      Result: and its dependency are downloaded to the directory c:\temp\download
    • Use the --from option to install a feature with its dependency from that directory; for example:
      featureManager install portletserving-2.0 --from=c:\temp\download --acceptLicense
      Result: Feature portletserving-2.0 and its dependency portlet-2.0 are installed as user features.
  • JMX REST connector The public APIs for direct REST access are available at https://<host>:<port>/IBMJMXConnectorREST/api
    The APIs support the JMX framework, file transfer, collective routing, and the newly added collective Liberty deployment URLs (with async support, multiple-host routing, custom actions, collective join, custom credentials, and post-transfer environment variables setup).
    This graph maps some of the URLs:

  • REST Handler SPI framework Collective routing is now supported for a single target. Other enhancements include variables in the URL, multiple URLs per handler, custom security, and custom collective routing:

  • Simplified download and install wizard In the past, multiple wizards and dialogs were launched in order to complete the download, installation, and creation of the Liberty profile runtime. We’ve simplified this into a single wizard to provide a smoother runtime and server creation experience.


And, of course, a bunch of bug fixes.

What’s already in there?

In the July/August beta, we fixed a whole bucketload of bugs. That was to make things more stable for all the stuff we added in previous betas, such as support Real-Time Communications (WebRTC) and CouchDB, there was JMS 2.0, JPA 2.1, bean validation 1.1, JSON-P 1.0, EJB 3.2 Lite, Servlet 3.1, OpenID Connect, Java 8 toleration, WebSockets, a facelift for the Liberty Repository

Go take a look at the previous beta announcements for a full list:

Get it now! Give feedback on dWAnswers

Join The Discussion

Your email address will not be published. Required fields are marked *