Release Notes and Known Issues

Red Hat Central provides wizards that generate skeletons and sample projects, enabling you to focus on developing the functionality of your applications. The wizards create web applications based on different APIs and technologies, showing the usage and advantages of each. JBoss Developer Studio also offers project file templates in a range of popular programming languages, including HTML, XHTML, and JSF.

Palettes in JBoss Developer Studio give access to the core elements of the JSF, RichFaces and Seam APIs, for use in developing the user interfaces of your applications. Elements of these APIs can be dragged and dropped directly into your project so that you can create richer user interfaces quickly. Visual Web Tools offers graphical and source viewing of files and defaults to dedicated editors for different file types. JBoss Developer Studio supports the Java EE specification and provides tools for JAX-RS, Hibernate, and CDI APIs so you can develop the server-side components of your applications effortlessly.

LiveReload Tools automatically refreshes browsers of local or deployed applications as you modify project resources to avoid needing to manually refresh. You can experience automatic refreshing when viewing applications in browsers on external and mobile devices, with application web addresses easy to navigate to with QR codes.

Mobile Web Tools provides support for HTML5 and jQuery Mobile to enable you to create web applications optimized across desktop and mobile clients. The HTML5 Project wizard in Red Hat Central generates a sample application using HTML5 and jQuery Mobile technologies and, together with HTML5 and jQuery Mobile project file templates, helps you to get up and running with these APIs and technologies quickly. HTML5 and jQuery Mobile widgets can be dragged from the jQuery Mobile palette into your project files and, in conjunction with the widget wizards, enable you to effortlessly develop customized user interfaces for your mobile web applications.

BrowserSim allows you to view your web applications on a variety of simulated mobile devices so that you can ensure they will be correctly formatted. LiveReload also extends to BrowserSim allowing you to experience automatic browser refreshing as you develop your mobile web applications. The integration of Firebug Lite and Weinre capabilities with BrowserSim assists you to inspect the page source of web pages with familiar tools.

Hybrid Mobile Tools provides support for developing and building Cordova-based hybrid mobile applications for iOS and Android platforms. The Hybrid Mobile application wizard assists you to quickly generate new projects, while the Cordova Configuration Editor and Cordova Plug-in Discovery wizard help you to efficiently modify the capabilities of your projects. Hybrid Mobile Tools provides actions that simplify your workflow, for example calling your system installed Android and iOS SDKs from within the IDE to emulate or run your hybrid mobile applications. With wizards to export workspace projects to Cordova-enabled native projects or ready-to-sign applications, you can quickly be ready to share your hybrid mobile projects and applications.

CordovaSim enables you to view and test your hybrid mobile applications on Android and iOS simulated mobile devices so that you can ensure they look and work as expected. You can interact with your mobile applications through BrowserSim and use the device input panel to provide sample data to your applications for device functions like cameras and accelerometers. An advantage of CordovaSim is that it does not require native SDKs to be installed on your system, unlike native SDK emulators. Additionally, by teaming the device control panel with BrowserSim, you get all of the great functionality of BrowserSim, such as skins and LiveReload, while simulating your hybrid mobile applications.

OpenShift Tools deploys your applications directly to the cloud on the Red Hat OpenShift platform. You can create and manage your OpenShift account and manage the deployment of applications to OpenShift within the IDE. In addition to using the OpenShift Application wizard to create and deploy new OpenShift applications, OpenShift Tools can import applications already deployed on OpenShift so that you can further develop them and manage their deployment from the comfort of the IDE.

A new server adapter has been added to support the next generation of CDK 3.2. While the server adapter itself has limited functionality, it is able to start and stop the CDK virtual machine via its minishift binary. Click Ctrl+3 (Cmd+3 on OSX) and type CDK to show a command to setup and/or launch the CDK server adapter. You should see the old CDK 2 server adapter and the new CDK 3 one (labeled Red Hat Container Development Kit 3.2+).

Figure 4.1. New CDK 3.2 Server Adapter

Set the credentials for your Red Hat account, the location of the CDK minishift binary file, the type of virtualization hypervisor and an optional CDK profile name.

Figure 4.2. Set the Credentials for CDK 3.2

After completion, a new CDK Server adapter will then be created and visible in the Servers view.

Figure 4.3. A New CDK Server Adapter Added

After the server is started, Docker and OpenShift connections should appear in their respective views, allowing the user to quickly create a new Openshift application and begin developing their AwesomeApp in a highly-replicatable environment.

Figure 4.4. New OpenShift Connection in the OpenShift Explorer View

Figure 4.5. New Docker Connection in the Docker Explorer View

A new command has been added to tune resource limits (CPU, memory) on an OpenShift deployment. It is available for a Service, a DeploymentConfig, a ReplicationController, or a Pod.

To activate it, in the OpenShift Explorer view, select the OpenShift resource, right-click and select Edit resource limits. The following dialog will appear:

Figure 4.6. Editing Resource Limits

After you change the resource limits for this deployment, it will be updated and new pods will be spawned (not for ReplicationController).

Figure 4.7. New Pods Created

When an OpenShift connection is created, the Docker registry URL is empty. When the CDK is started through the CDK server adapter, an OpenShift connection is created or updated if a matching OpenShift connection is found. If you have several OpenShift connections the remaining ones will be left with the empty URL.

You can find the matching Docker registry URL when editing the OpenShift connection through the Discover button.

Figure 4.8. Finding Matching Docker Registry URLs

Click the Discover button and the Docker registry URL will be auto filled if a matching started CDK server adapter is found.

Figure 4.9. Auto Filled Docker Registry URL

It is possible to login from JBoss Tools to OpenShift.io. A single account will be maintained per workspace. Once you initially logged onto OpenShift.io, all needed account information (tokens,…​) will be stored securely.

There are two ways to login onto OpenShift.io:

4.1.4.1. UI Based Login to OpenShift.io

Link kopieren

Click the new icon Toolbar to login.

If this is the first time you are logging in to OpenShift.io or if your OpenShift.io account tokens are not valid anymore, you will see a browser launched with the following content:

Figure 4.10. UI Based Login to OpenShift.io

Enter your RHDP login and the browser will then auto-close and an extract of the OpenShift.io token will be displayed (for security reasons).

Figure 4.11. Extract of OpenShift.io Token

This dialog will be also shown if an OpenShift.io account was configured in the workspace and the account information is valid.

4.1.4.2. Via Extension Point

Link kopieren

The OpenShift.io integration can be invoked by a third party service through the org.jboss.tools.openshift.io.code.tokenProvider extension point. This extension point will perform the same actions as the UI but will return an access token for OpenShift.io to the third party service. A detailed explanation of how to use this extension point is described on the Wiki page.

You can display the account information using the Eclipse Jboss Tools > OpenShift.io preference node. If you workspace does not contain an OpenShift.io account yet, you should see the following.

Figure 4.12. OpenShift.io Account Not Configured

If you have a configured OpenShift.io account, you should see the following.

Figure 4.13. OpenShift.io Account Configured

A server adapter has been added to work with EAP 7.1 and Wildfly 11. It is based on WildFly 11. This new server adapter includes support for incremental management deployment like its upstream WildFly 11 counterpart.

It is now possible to set Bean references from the User Interface when creating a new Bean.

Figure 4.14. Setting Bean References

Editing Bean references is also available in the Properties view when editing an existing Bean.

Figure 4.15. Setting Bean References in the Properties View

Additional validation has been added to help users avoid mixing Beans defined with class names and Beans defined referencing other beans.

You can now download and install Apache Karaf 4.0 and 4.1 server adapters from within your development environment.

Figure 4.16. New Apache Karaf Server Adapters

You can now change the Apache Camel version used in your project. For this, invoke the context menu of the project in the Project Explorer view and navigate to the Configure menu. Here, the Change Camel Version menu entry will guide you through this process.

Figure 4.17. Switch Apache Camel Version

The validation in the editor has been improved to find containers that lack mandatory child elements (for instance a Choice without a child element).

Figure 4.18. Improved Validation

Java™ 9 is here, and JDT fully supports it:

JUnit 5 support is now available in Eclipse.