Chapter 4. New Features and Enhancements

Fuse Tooling was previously a part of Red Hat JBoss Developer Studio Integration Stack. For easier availability of development of Fuse integration projects, it is now a part of Red Hat JBoss Developer Studio. For an overview, see https://tools.jboss.org/features/fusetools.html.

Fuse Tooling is now also available in Red Hat Central.

Figure 4.1. Fuse in DevStudio

View larger image

We are happy to finally announce support for Beans (Spring/Blueprint).

Using the Route Editor you can now access Spring / Blueprint Beans in your Camel Context through the Configurations tab.

Figure 4.2. Bean Support

View larger image

In the Configurations tab you can see all global configuration elements of your Camel Context. You can add, edit and delete elements using the buttons on the right side.

Figure 4.3. Edit Elements

View larger image

Click Add or Edit to open a wizard to guide you on creation of the Bean.

Figure 4.4. Add or Edit Wizards

View larger image

In the wizard you can select an existing bean class from your project or create a new bean class. You can also specify constructor arguments and bean properties. Once created you can then modify the properties of that Bean in the Properties view.

Figure 4.5. Modify Bean Properties

View larger image

The Seam component has been marked deprecated because the Seam project has been stopped. It is still available in Red Hat Central and may be removed in the future.

The included Forge runtime is now 3.7.2.Final. For the official announcement, see this.

Some operations (logs, file synchronization) require the use of the oc CLI client. You could specify a single instance of the used oc CLI tool for the whole workspace. This could cause trouble when working simultaneously with several OpenShift clusters (that may have different version levels). It is now possible to specify the oc CLI tool on the connection level. This is optional and the default is to use the oc CLI tool specified at the workspace level.

The connection specific oc CLI tool is accessible through the Edit OpenShift Connection dialog box using the Advanced button.

Figure 4.6. Advanced Button

View larger image

Enable the Override 'oc' location' flag and select a specific oc CLI tool for this connection through the Browse button.

Figure 4.7. Browse Button for CLI

View larger image

OpenShift connections created by the CDK server adapter will automatically have a specific oc CLI tool set as the CDK installs locally an oc CLI tool that is aligned with the embedded OpenShift version.

Figure 4.8. An Automatically Set oc CLI Tool

View larger image

The OpenShift server and Kubernetes server versions are now displayed in the OpenShift connection properties. This information is retrieved using an un-authenticated request and logging in to the OpenShift cluster is not required. This allows the user to verify the OpenShift and Kubernetes level when interacting.

Here is an example based on an OpenShift connection against CDK3:

Figure 4.9. OpenShift and Kubernetes Server Versions Displayed

View larger image

No values are displayed if the cluster is not started or accessible.

Figure 4.10. No Values Displayed

View larger image

The Freemarker component has been marked deprecated as there is no more maintenance on the source code. It is still available in Red Hat Central and may be removed in the future.

Related JIRA: JBIDE-24484

We are glad to announce the support of the Hibernate Search. The project was started by Dmitrii Bocharov in the Google Summer Code program and has been successfully transferred in the current release of the JBoss Tools from Dmitrii’s repository into the jbosstools-hibernate repository and has become a part of the JBoss family of tools.

4.5.1.1. Functionality

Link kopieren

Two options were added to the console configurations submenu: Index Rebuild and Index Toolkit. These option are available when you use hibernate search libraries (they exist in the build path of your application, e.g. via maven).

Figure 4.11. Index Rebuild Menu Option

View larger image

4.5.1.2. Index Rebuild

Link kopieren

When introducing Hibernate Search in an existing application, you have to create an initial Lucene index for the data already present in your database.

The option Index Rebuild will do this by re-creating the Lucene index in the directory specified by the hibernate.search.default.indexBase property.

Figure 4.12. Creating the Lucene Index

View larger image

Figure 4.13. hibernate.cfg.xml File

View larger image

4.5.1.3. Index Toolkit

Link kopieren

The Open Index Toolkit submenu of the console configuration opens an Index Toolkit view, which has three tabs: Analyzers, Explore Documents, Search.

4.5.1.3.1. Analyzers

Link kopieren

This tab allows you to view the result of the work of different Lucene Analyzers. The combo-box contains all classes in the workspace which extend org.apache.lucene.analysis.Analyzer, including custom implementations created by the user. While you type the text you want to analyse, the result immediately appears on the right.

Figure 4.14. Analyzers Tab

View larger image

4.5.1.3.2. Explore Documents

Link kopieren

After creating the initial index you can now inspect the Lucene Documents it contains.

All entities annotated as @Indexed are displayed in the Lucene Documents tab. Click the checkboxes as needed and load the documents. Iterate through the documents using arrows.

Figure 4.15. Index Toolkit Tab

View larger image

4.5.1.3.3. Searching

Link kopieren

The plugin passes the input string from the search text box to the QueryParser which parses it using the specified analyzer and creates a set of search terms, one term per token, over the specified default field. The result of the search pulls back all documents which contain the terms and lists them in a table below.

Search Tab image::search.png[Search Tab]

4.5.1.3.4. Demo

Link kopieren

To see a demo of the Hibernate Search Pluging, see the demo.

A server adapter has been added to work with EAP 7.1. It’s currently released as a Tech-Preview feature, since the underlying WildFly 11 continues to be under active development with substantial opportunity for breaking changes. This new server adapter includes support for incremental management deployment like it’s upstream WildFly 11 counterpart.

Related JIRA: JBIDE-24508

The Event Log view has been removed. The standard eclipse log is to be used for errors and other important messages regarding errors during server state transitions.

Related JIRA: JBIDE-22717

Support has been added to the Run a Docker Image wizard to add a basic security option. When chosen, this option behaves the same as using docker run --cap-drop=all --readonly --tmpfs /run --tmpfs /tmp. In addition to dropping extraneous capabilities, the basic option makes all non-mounted directories read-only and mounts /run and /tmp into tmpfs which is cleared on each start of the container.

Figure 4.16. Run a Docker Image Wizard

View larger image

The Eclipse Docker Tooling Feature now contains a plugin that integrates with the Java Development Tools (JDT). This permits the running and debugging of Eclipse Java projects within containers. The functionality is provided through the context menu under the Run As and Debug As options. The daemon connection used, as well as the image chosen are configurable through launch configurations.

Figure 4.17. Debug As and Run As Menu Options

View larger image

This is intended to work in the same way that a regular run/debug session works.

Figure 4.18. Debugging a File

View larger image