Here’s the latest WebSphere Liberty beta and WebSphere Developer Tools (WDT).

Thanks to your support for our regular beta programme, we are able to release new Liberty features every few months. Most recently, in March.

Look out for more betas over the coming months.

Get it now! Ask a question about the beta

What’s in the WebSphere Liberty beta for March?

Rapid development using the Liberty Maven plugin and WDT for Eclipse

We’ve made significant updates to the liberty-maven-plugin and Eclipse tools to improve the developer experience when working with WebSphere Liberty in a Maven environment. The liberty-maven-plugin has been updated to include Loose Application support for web applications that enables the WebSphere Liberty runtime to process updates lightning fast! The Eclipse tools can now detect Maven web application projects that are configured to work with the new liberty-maven-plugin and will automatically create a server in the workbench. You can then iteratively develop and debug your web application within Eclipse and then build and package your application using Maven. The end result is a cohesive Maven development experience. We’ve got more coming so stay tuned for updates! Let us know what you think on the WASDev community forums.

To try out the new experience simply follow these steps:

  • Add the following content to a new or existing settings.xml file in the ${user.home}/.m2 folder:

        <name>Sonatype Snapshots Repository</name>
         <name>Sonatype Nexus Snapshots</name>

  • Use the following command to generate the sample project from an archetype:
    mvn archetype:generate -DarchetypeGroupId=net.wasdev.wlp.maven -DarchetypeArtifactId=liberty-archetype-webapp -DarchetypeVersion=2.0-SNAPSHOT -DgroupId=ServletSample -DartifactId=ServletSample -Dversion=1.0

  • Run mvn install on your project

  • Import your project into the WDT March Beta using File > Import… > Existing Maven Projects

After importing your project a server will get automatically generated in the Servers view with your application already published.

You can now efficiently develop your application within the workbench whilst reaping the benefits of Maven.

Here are some things you can try:

  • Run your web application by opening the context menu on a resource in the Project Explorer view and selecting Run As > Run On Server.
  • Make updates to a resource and see the server pick up the changes on-the-fly.
  • Debug your web application by setting a breakpoint in your code and using the Debug As > Debug On Server action.
  • Perform actions like Start, Stop, and Open Log Files on the generated server in the Servers view.
  • If you run mvn clean, or any other goal from within the workbench that causes the Liberty files to be deleted, the server and its associated runtime will be automatically removed from the workbench. Running mvn install or one of the liberty-maven-plugin goals that re-installs the server will reinstate the server in the Servers view. Note: Maven commands executed from outside of Eclipse will require refreshing the Project Explorer view in order for the workbench to process the changes.

MicroProfile Config feature

With the microProfileConfig-0.1 feature, you can directly use the Config APIs to retrieve configuration without the need to know where the properties are defined. The properties can be dynamically updated and then retrieved by the applications without the application restarting. The configuration can be located in multiple sources, and has a priority system. If the same property is specified in multiple config sources, the value from the config source with the highest priority will be used. The properties can be overwritten by users in different environments.

MicroProfile Fault Tolerance feature

With the microProfileFaultTolerance-0.1 feature, you can make the service invocation resilient via retry, fallback, timeout, circuit breaker and bulkhead functionalities. If a service invocation fails, a retry can be performed. After some retries, a fallback operation can be specified. Indefinite waiting is no longer a problem as the timeout can be specified on service invocation. Repeating timeouts are solved by the functionality of the circuit breaker. You will not need to package fault tolerance libraries into your applications any more.

What’s already in there?

The February 2017 beta included JPA container 2.1, Transport Security 1.0, an Admin Center update, Logstash Collector and Bluemix Log Collector updates, a Liberty: Audit extension, the isoDateFormat option and a Spnego 1.0 update.

Take a look at the previous beta announcements for a full list of stuff added since the release in June 2016:

Get it now! Ask a question on Stack Overflow

1 comment on"Beta: WebSphere Liberty and tools (March 2017)"

  1. […] but now additional APIs are being defined. You can start to see the results of this work in the Liberty March beta where there are new features for injecting environmental configuration and utilizing fault […]

Join The Discussion

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