Attention desktop IDE users: Red Hat Developer Studio 12.9 and the community edition, JBoss Tools 4.9.0 for Eclipse 2018-09, are now available. You can download the Developer Studio bundled installer, which installs Eclipse 4.9 with all of the JBoss Tools already configured. Or, if you have an existing Eclipse 4.9 (2018-09) installation, you can download the JBoss Tools package.
This article highlights some of the new features in both JBoss Tools and Eclipse Photon, covering WildFly, Spring Boot, Camel, Maven, and many Java-related improvements—including full Java 11 support.
Developer Studio/JBoss Tools provides a desktop IDE with a broad set of tooling covering multiple programming models and frameworks. If you are doing container/cloud development, there is integrated functionality for working with Red Hat OpenShift, Kubernetes, Red Hat Container Development Kit, and Red Hat OpenShift Application Runtimes. For integration projects, there is tooling covering Camel and Red Hat Fuse that can be used in both local and cloud deployments.
Continue reading “Announcing Red Hat Developer Studio 12.9.0.GA and JBoss Tools 4.9.0.Final for Eclipse 2018-09”
SOAP-based services are plentiful in many enterprise solutions and are slowly being replaced by RESTful services to simplify their use. There is a new wizard to help you make the transition with Apache Camel’s Rest DSL added in the latest version of Red Hat Fuse Tooling. This article shows how to use the new wizard to transition from older SOAP-based services to more modern REST-based services.
If you aren’t familiar, Red Hat Fuse is an integration platform based on Camel and a number of other projects. The updating Fuse Tooling is available in Red Hat Developer Studio 12.0.0, the desktop IDE that is based on Eclipse 4.8 Photon. You can also get the new wizard by adding JBoss Tools 4.6 to your existing Eclipse 4.8 Photon installation by downloading it directly, or installing via the Eclipse Marketplace.
Continue reading “How to migrate your SOAP web service to REST with Camel”
Attention desktop IDE users: Red Hat Developer Studio 12.0 and the community edition, JBoss Tools 4.6.0 for Eclipse Photon, are now available. You can download a bundled installer, Developer Studio, which installs Eclipse 4.8 with all of the JBoss Tools already configured. Or, if you have an existing Eclipse 4.8 (Photon) installation, you can download the JBoss Tools package. This article highlights some of the new features in both JBoss Tools and Eclipse Photon, covering WildFly, Spring Boot, Camel, Maven, and many Java related improvements including full Java 10 support.
Developer Studio / JBoss Tools provides a desktop IDE with a broad set of tooling covering multiple programming models and frameworks. If you are doing container / cloud development, there is integrated functionality for working with Red Hat OpenShift, Kubernetes, Red Hat Container Development Kit, and Red Hat OpenShift Application Runtimes. For integration projects, there is tooling covering Camel and Red Hat Fuse that can be used in both local and cloud deployments.
Continue reading “Announcing Red Hat Developer Studio 12.0.0.GA and JBoss Tools 4.6.0.Final for Eclipse Photon”
Discoverability and ease of installation of Apache Camel tooling based on the Language Server Protocol has been improved. Manual download and installation of binaries is no longer necessary! For the Eclipse desktop IDE and the VS Code environment you can now find and install the Camel tooling directly from the marketplaces for each development environment.
Camel Language Server is now also available in Red Hat OpenShift.io!
In this article, I will show you how you can install Camel tooling via the marketplaces for Eclipse and VS Code. I will also show how to enable Camel tooling in your OpenShift.io workspace.
Continue reading “Apache Camel URI completion: easy installation for Eclipse, VS Code, and OpenShift.io”
In case you missed it, Jakarta EE is officially out! Java EE was given a new home at the Eclipse Foundation and on February 26, 2018 Jakarta EE was chosen as the new name for Java EE. Join us at the next online DevNation Live Tech Talk on Thursday, May 3rd at 12pm EDT. The topic is “Jakarta EE: The Future of Java EE” presented by Dr. Mark Little, and hosted by Burr Sutter.
Java EE has been the dominant enterprise Java standard for well over a decade. With the release of Jakarta EE, we all have a chance to collaborate and build on the good things it inherits, while working to evolve those pieces that were perhaps never quite what was needed.
What does this mean for the future of enterprise Java and traditional Java application servers? Join us to gain an understanding of where Jakarta EE is heading and how you can help drive the future of enterprise Java.
Register now and join the live presentation at 12pm EDT, Thursday, May 3rd.
Continue reading “Next DevNation Live: Jakarta EE: The Future of Java EE, May 3rd, 12pm EDT”
The community editions of JBoss Tools 4.5.3 and JBoss Developer Studio 11.3 for Eclipse Oxygen.3a are here waiting for you. Check it out!
JBoss Developer Studio comes with everything pre-bundled in its installer. Simply download it from our JBoss Products page and run it like this:
java -jar jboss-devstudio-<installername>.jar
JBoss Tools or Bring-Your-Own-Eclipse (BYOE) JBoss Developer Studio require a bit more:
This release requires at least Eclipse 4.7 (Oxygen) but we recommend using the latest Eclipse 4.7.3a Oxygen JEE Bundle since then you get most of the dependencies preinstalled.
Once you have installed Eclipse, you can either find us on the Eclipse Marketplace under “JBoss Tools” or “Red Hat JBoss Developer Studio”.
For JBoss Tools, you can also use our update site directly.
What is new?
Continue reading “Announcing Developer Studio 11.3.0.GA, JBoss Tools 4.5.3 for Eclipse Oxygen.3a”
Every developer has the goal of building the most resilient application possible. Due to the distributed nature of microservices, resiliency and handling failures gracefully is mandatory. The Java ecosystem has some nice frameworks for fault tolerance, such as Hystrix or Failsafe. However, none of these provide a standard API, so using them means your application will be tightly coupled to that framework. The primary motivation for the MicroProfile specifications is to provide standard APIs that eliminates the tight coupling and improves deployment flexibility. This article will describe the main features of the MicroProfile Fault Tolerance specification, and then demonstrate how it was implemented in WildFly Swarm, the Red Hat MicroProfile implementation.
Continue reading “MicroProfile Fault Tolerance in WildFly Swarm”
The JBoss Tools OpenShift tooling uses rsync to sync files between your local workstation and the running pods on an OpenShift cluster. This is used by the OpenShift server adapter to provide hot deploy and debugging features for the developer. If you’re running Red Hat JBoss Developer Studio or JBoss Tools on Windows, there are some issues with file permissions that can be painful. These problems are due to file permission model used on the underlying Windows filesystem being different than the model used by Linux. Linux and macOS users won’t run into these problems. The aim of this article is to explain the root cause and how to fix it.
Continue reading “Avoiding Windows rsync permission problems with Red Hat JBoss Developer Studio”
The community editions of JBoss Tools 4.5.2 and JBoss Developer Studio 11.2 for Eclipse Oxygen.2 are here waiting for you. Check it out!
Continue reading “Announcing Developer Studio 11.2.0.GA and JBoss Tools 4.5.2.Final for Eclipse Oxygen.2”
The OpenShift Online Starter platform is available for free: visit https://manage.openshift.com/. It is based on Red Hat OpenShift Container Platform 3.7. This offering allows you to play with OpenShift Container Platform and deploy artifacts. The purpose of the article is to describe how to use Red Hat JBoss Developer Studio or JBoss Tools together with this online platform.
Continue reading “Develop and Deploy on OpenShift Online Starter using Red Hat JBoss Developer Studio”