Thanks for all your support for our beta program so far. Here’s the latest beta of WebSphere® Application Server Liberty Profile and WebSphere Developer Tools (WDT).

And, you know what? With the introduction of the JSF 2.2 support, the March Beta now provides implementations for all of the major technologies that make up Java EE 7 Web Profile!

Look out for more betas over the coming months. Some of the features in previous betas are now available and supported in production in WebSphere Application Server Liberty Profile V8.5.5.

Get it now! Give feedback on dWAnswers

What’s in the Liberty beta for March 2015?

In the March 2015 Liberty beta, we’ve added the following goodies for you…

Java EE 7

  • JavaServer Faces (JSF) We now have initial support for JSF (JavaServer Faces) 2.2! The major features of JSF 2.2 include:
    • Faces Flow
    • Resource Library Contracts
    • HTML5 Friendly Markup Support
  • Remote EJBs Enables the use of remote EJB interfaces. Like other EJB 3.2 capabilities, this feature is included by the ejb-3.2 feature.
    • If the ejbHome-3.2 feature is used in addition to ejbRemote-3.2, EJBHome interfaces are also supported.
    • Unfortunately, some spurious CWWKG0033W warnings snuck in just before the beta, but these should be harmless, so we wanted to let people experiment rather than holding it out.


  • assetManager updated The assetManager was introduced in the February beta. In this beta, you can use the viewSettings action to view your configuration, use the testConnection action to test repository connections, and use the find action to search for different types of assets, such as feature, sample, and open source integration.
  • Java batch role-based security You can now secure the Liberty batch environment using role-based security. Users can be a part of one or more possible batch roles: batchAdmin, batchSubmitter, and batchMonitor. By configuring a user registry and authorization roles an administrator can restrict access to batch operations and job instance data through the batch REST API or JobOperator interface.
  • Java batch multi server support Make job operations that submit to one server available to other servers too. Use JMS to configure batch dispatcher and batch endpoint.

Knowledge Center

And, of course, a bunch of bug fixes.

What’s already in there?

In the February beta, we added CDI 1.2, JSP 2.3 and EL 3.0, application client 1.0, JASPIC 1.1, JACC 1.5, and EJB 3.2. Plus operations, WebSphere Developer Tools, and Admin Center updates.

In earlier betas, we added SIP Servlets 1.1 and tools, SPNEGO support, OSGi App integration, JDBC 4.1, OSGi & Web 3.1 facet configuration for OSGi bundles, and JAX-RS 2.0 client wizard; we fixed a shedload of bugs and added things like support for remote development, auto-scaling and dynamic routing, Real-Time Communications (WebRTC) and CouchDB; finally, there was JAX-RS 2.0, Java Batch, JMS 2.0, JPA 2.1, bean validation 1.1, JSON-P 1.0, EJB 3.2 Lite, concurrent-1.0, 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 *