Red Hat JBoss Developer Studio 11.3

Transcription

1 Red Hat JBoss Developer Studio 11.3 Release Notes and Known Issues Highlighted features in 11.3 Last Updated:

2

3 Red Hat JBoss Developer Studio 11.3 Release Notes and Known Issues Highlighted features in 11.3 Supriya Takkhi

4 Legal Notice Copyright 2018 Red Hat, Inc. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. Linux is the registered trademark of Linus Torvalds in the United States and other countries. Java is a registered trademark of Oracle and/or its affiliates. XFS is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries. MySQL is a registered trademark of MySQL AB in the United States, the European Union and other countries. Node.js is an official trademark of Joyent. Red Hat Software Collections is not formally related to or endorsed by the official Joyent Node.js open source or commercial project. The OpenStack Word Mark and OpenStack logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community. All other trademarks are the property of their respective owners. Abstract This document lists and briefly describes new and improved features of Red Hat JBoss Developer Studio 11.3.

5 Table of Contents Table of Contents. CHAPTER INTRODUCTION TO... RED..... HAT..... JBOSS DEVELOPER STUDIO ABOUT RED HAT JBOSS DEVELOPER STUDIO USE CASES OF JBOSS DEVELOPER STUDIO Web Applications Web Applications Optimized for Mobile Devices Hybrid Mobile Applications Applications for Cloud Deployment ABOUT THIS RELEASE ECLIPSE AUTOMATED REPORTING INTERFACE (AERI) 5. CHAPTER RELEASE NOTES GENERAL Credentials Framework Sunsetting jboss.org Credentials ARQUILLIAN Arquillian component removal AEROGEAR Aerogear Component Deprecation BROWSERSIM BrowserSim Component Deprecation FREEMARKER Freemarker Component Removal FUSE TOOLING New Shortcuts in the Fuse Integration Perspective Performance improvement: Loading Advanced tab for Camel Endpoints Display Fuse Version Corresponding to Camel Version Proposed Update Validation for Similar IDs Between a Component and its Definition Improved Guidance in Method Selection for Factory Methods on Global Bean Customize EIP Labels in the Diagram Fuse Ignite Technical Extension Templates Improvements in the Wizard to Create a Fuse Integration Project Camel Rest DSL Editor (Technical Preview) Dozer Upgrade and Migration HIBERNATE TOOLS Hibernate Runtime Provider Updates New Hibernate 5.3 Runtime Provider Other Runtime Provider Updates LIVERELOAD LiveReload Component Deprecation OPENSHIFT Minishift Server Adapter CDK and Minishift Server Adapter Better Developer Experience CDK and Minishift Server Adapter Runtime Download CDK Server Adapter Integrated Setup 33. CHAPTER ISSUES RESOLVED ISSUES KNOWN ISSUES RED HAT JBOSS FUSE RELATED ISSUES 34. CHAPTER ADDITIONAL RESOURCES

6 Red Hat JBoss Developer Studio 11.3 Release Notes and Known Issues 2

7 CHAPTER 1. INTRODUCTION TO RED HAT JBOSS DEVELOPER STUDIO CHAPTER 1. INTRODUCTION TO RED HAT JBOSS DEVELOPER STUDIO 1.1. ABOUT RED HAT JBOSS DEVELOPER STUDIO JBoss Developer Studio is a set of Eclipse-based development tools. It contains plug-ins that integrate with Eclipse to extend the existing functionality of the integrated development environment (IDE). JBoss Developer Studio is designed to increase your productivity when developing applications. You can focus on building, testing, and deploying your applications because JBoss application development tools are integrated in one IDE. JBoss Developer Studio can also assist your application development with its unique features in the following ways: Develop new applications using the wizards and project examples of Red Hat Central Add powerful functionality to applications with minimal effort using Forge Tools Build web interfaces with ease using the visual editing and drag-and-drop utilities of Visual Web Tools and Mobile Web Tools Experience browsers automatically refreshing in response to modified application resources with LiveReload Tools Incorporate Hibernate, CDI, JAX-RS, JSF, Seam, and other popular APIs into applications with simplicity using the tool-driven interface Preview and test mobile web applications on a variety of simulated mobile devices using BrowserSim Create, build, and test Cordova-based hybrid mobile applications for ios and Android platforms using Hybrid Mobile Tools and CordovaSim Deploy applications to JBoss runtime servers and the cloud using JBoss Server Tools and OpenShift Tools JBoss Developer Studio is built around Eclipse and packaged with all the necessary dependencies and third-party plug-ins for simplified installing. For developers already running Eclipse, JBoss Developer Studio can also be installed through Eclipse Marketplace. Installing JBoss Developer Studio in an existing Eclipse installation is referred to as BYOE (Bring Your Own Eclipse) USE CASES OF JBOSS DEVELOPER STUDIO JBoss Developer Studio assists Java EE developers by integrating JBoss technology and APIs in a single development environment. Here are a few ways that JBoss Developer Studio helps make development easier: Web Applications 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. 3

8 Red Hat JBoss Developer Studio 11.3 Release Notes and Known Issues 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 Web Applications Optimized for Mobile Devices 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 Applications 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 Applications for Cloud Deployment 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 4

9 CHAPTER 1. INTRODUCTION TO RED HAT JBOSS DEVELOPER STUDIO 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 ABOUT THIS RELEASE Red Hat JBoss Developer Studio 11.3 is an update of Red Hat JBoss Developer Studio 11.2 and it has the following features: It includes Eclipse Oxygen.3a. It requires a minimum of Java 8 to run. It introduces new features, which are outlined in the New Features section. It contains new features for the existing tools. It resolves issues identified in earlier versions of JBoss Developer Studio. For more information about operating systems, chip architectures and Java developer kits supported by this release, see Supported Configurations and Components page on the Red Hat Customer Portal ECLIPSE AUTOMATED REPORTING INTERFACE (AERI) To contribute to JBoss Tools, we recommend you to enable the Eclipse Automated Reporting Interface (AERI) in JBoss Tools. To read about configuring error reporting in JBoss Tools, see: 5

10 Red Hat JBoss Developer Studio 11.3 Release Notes and Known Issues 2.1. GENERAL CHAPTER 2. RELEASE NOTES Credentials Framework Sunsetting jboss.org Credentials Download Runtimes and CDK Server Adapter used the credentials framework to manage credentials. However, the JBoss.org credentials cannot be used any more as the underlying service used by these components does not support these credentials. The credentials framework still supports the JBoss.org credentials in case other services/components require or use this credentials domain ARQUILLIAN Arquillian component removal The Arquillian component has been removed from Red Hat Central as it has been deprecated since July The last available update site release is at Arquillian v Related JIRA: JBIDE AEROGEAR Aerogear Component Deprecation The Aerogear 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 BROWSERSIM BrowserSim Component Deprecation The BrowserSim 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 FREEMARKER Freemarker Component Removal The Freemarker component has been removed from Red Hat Central as it has been deprecated since July

11 CHAPTER 2. RELEASE NOTES The last available update site release is at Freemarker v Related JIRA: JBIDE FUSE TOOLING New Shortcuts in the Fuse Integration Perspective Shortcuts for the Java, Launch, and Debug perspectives and basic navigation operations are now provided within the Fuse Integration perspective. The result is a set of buttons in the Toolbar. Figure 2.1. Shortcuts in the Fuse Integration Perspective All the associated keyboard shortcuts are also available, such as Ctrl+Shift+T to open a Java Type Performance improvement: Loading Advanced tab for Camel Endpoints The loading time of the Advanced tab in the Properties view for Camel Endpoints is improved. 7

12 Red Hat JBoss Developer Studio 11.3 Release Notes and Known Issues Figure 2.2. Loading Time for the Advanced Tab Previously, in case of Camel Components that had too many parameters, it took several seconds to load the Advanced tab. For example, for the File component, it would take ~3.5 seconds. It now takes ~350ms. The load time has been reduced by a factor of 10. (See this article on the response time.) If you notice other places showing slow performance, file a report by using the Fuse Tooling issue tracker. The Fuse Tooling team appreciates your help. Your feedback contributes to our development priorities and improves the Fuse Tooling user experience Display Fuse Version Corresponding to Camel Version Proposed When you create a new project, you select the Camel version from a list. Now, the list of Camel versions includes the Fuse version to help you choose the version that corresponds to your production version. 8

13 CHAPTER 2. RELEASE NOTES Figure 2.3. Fuse Version Corresponding to Camel Version Update Validation for Similar IDs Between a Component and its Definition Starting with Camel 2.20, you can use similar IDs for the component name and its definition unless the specific property registerendpointidsfromroute is provided. The validation process checks the Camel version and the value of the registerendpointidsfromroute property. For example: <from id="timer" uri="timer:timername"/> Improved Guidance in Method Selection for Factory Methods on Global Bean When selecting factory method on a Global bean, too many possibilities were proposed in the user interface. The list of factory methods for a global bean is now limited to only those methods that match the constraints of the bean s global definition type (bean or bean factory) Customize EIP Labels in the Diagram The Preferences window for the Fuse Tooling, Editor view includes a new Preferred Labels option. 9

14 Red Hat JBoss Developer Studio 11.3 Release Notes and Known Issues Figure 2.4. Preferred Labels Option Use this option to define the label of EIP components (except endpoints) shown in the Editor s Design view. Figure 2.5. Defining the Label of EIP Components Fuse Ignite Technical Extension Templates The existing template for "Custom step using a Camel Route" has been updated to work with Fuse 7 Tech Preview 4. Two new templates are added: Custom step using Java Bean and Custom connector. 10

15 CHAPTER 2. RELEASE NOTES Figure 2.6. New Fuse Ignite Technical Extension Templates Improvements in the Wizard to Create a Fuse Integration Project The creation wizard provides better guidance for the targeted deployment environment. 11

16 Red Hat JBoss Developer Studio 11.3 Release Notes and Known Issues Figure 2.7. Better Guidance in Creating a Fuse Integration Project More place is available to choose the templates and the templates are now filtered based on the targeted environment. 12

17 CHAPTER 2. RELEASE NOTES Figure 2.8. Better Filtering of Templates The Where you can find more examples to use as templates? link, at the bottom of the Advanced Project Setup window, points to other places where you can find different examples for advanced users Camel Rest DSL Editor (Technical Preview) Camel now provides a Rest DSL to help the integration through Rest endpoints. Fuse Tooling now has a new tab in the read-only mode to visualize the Rest endpoints defined. 13

18 Red Hat JBoss Developer Studio 11.3 Release Notes and Known Issues Figure 2.9. Camel Rest DSL Editor It is currently in Technology Preview and needs to be activated in the Window Preferences Fuse Tooling Editor Enable Read Only Tech preview REST DSL tab. This is a work in progress feature. To add your feedback, add a comment in this epic JIRA Dozer Upgrade and Migration When upgrading from Camel 2.20 or lower to Camel 2.20 or higher, the Dozer dependency has been upgraded to a version that is not backward-compatible. If you open a Data transformation based on Dozer in Fuse Tooling, it will propose to migrate the file used for the transformation (technically changing the namespace). It allows you to continue to use the Data Transformation editor and have, in most cases, the Data Transformation working at runtime with Camel 2.20 or higher HIBERNATE TOOLS Hibernate Runtime Provider Updates A number of additions and updates have been performed on the available Hibernate runtime providers New Hibernate 5.3 Runtime Provider With beta releases available in the Hibernate 5.3 stream, a corresponding Hibernate 5.3 runtime provider is now available. This runtime provider incorporates Hibernate Core version Beta2 and Hibernate Tools version Beta1. 14

19 CHAPTER 2. RELEASE NOTES Figure Hibernate 5.3 Runtime Provider Other Runtime Provider Updates The Hibernate 5.0 runtime provider now incorporates Hibernate Core version Final and Hibernate Tools version Final. The Hibernate 5.1 runtime provider now incorporates Hibernate Core version Final and Hibernate Tools version Final. The Hibernate 5.2 runtime provider now incorporates Hibernate Core version Final and Hibernate Tools version Final LIVERELOAD LiveReload Component Deprecation The LiveReload 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 OPENSHIFT Minishift Server Adapter A new server adapter has been added to support upstream Minishift. While the server adapter itself has limited functionality, it is able to start and stop the Minishift virtual machine via its minishift binary. From the Servers view, click New and then type minishift, that will bring up a command to setup and/or launch the Minishift server adapter. 15

20 Red Hat JBoss Developer Studio 11.3 Release Notes and Known Issues Figure Define a New Minishift Server You must set the location of the minishift binary file, the type of virtualization hypervisor and an optional Minishift profile name. 16

21 CHAPTER 2. RELEASE NOTES Figure Setting the Minishift Values After you have completed the above steps, a new Minishift Server adapter is created and visible in the Servers view. Figure Minishift Server Listed in the Servers View 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. 17

22 Red Hat JBoss Developer Studio 11.3 Release Notes and Known Issues Figure Docker and OpenShift Connections in their Respective Views Related JIRA: JBIDE CDK and Minishift Server Adapter Better Developer Experience When working with both CDK and upstream Minishift, it is recommanded to distinguish environments through the MINISHIFT_HOME variable. Initially, it was possible to use this parameter but it required a two-step process: 1. Create the server adapter (through the wizard). 2. Change the MINISHIFT_HOME in the server adapter editor. It is now possible to set this parameter from the server adapter wizard. So now, everything is correctly setup when you create the server adapter. Following is an example with the CDK server adapter. 1. From the Servers view, click New Server and enter cdk in the filter field. 18

23 CHAPTER 2. RELEASE NOTES Figure Defining a New Server 2. Select Red Hat Container Development Kit

24 Red Hat JBoss Developer Studio 11.3 Release Notes and Known Issues Figure Selecting Red Hat Container Development Kit Click Next. 20

25 CHAPTER 2. RELEASE NOTES Figure Completing the Container Development Kit 3.2 Setup The MINISHIFT_HOME parameter can be set here and used as the default. Related JIRA: JBIDE CDK and Minishift Server Adapter Runtime Download Until now, you needed a previously downloaded CDK or Minishift binary, when working with both CDK and upstream Minishift. It is now possible to download the runtime to a specific folder when you create the server adapter. Following is an example of the CDK server adapter. 1. From the Servers view, click New Server and type cdk in the filter field. 21

26 Red Hat JBoss Developer Studio 11.3 Release Notes and Known Issues Figure Defining a New Server 2. Select Red Hat Container Development Kit

27 CHAPTER 2. RELEASE NOTES Figure Selecting Red Hat Container Development Kit Click Next. 23

28 Red Hat JBoss Developer Studio 11.3 Release Notes and Known Issues Figure Completing the Container Development Kit 3.2 Setup 4. To download the runtime, click the Download and install runtime link. 24

29 CHAPTER 2. RELEASE NOTES Figure Download the CDK Runtime 5. Select the version of the runtime you want to download. 25

30 Red Hat JBoss Developer Studio 11.3 Release Notes and Known Issues Figure Selecting the CDK Runtime Version 6. Click Next. 26

31 CHAPTER 2. RELEASE NOTES Figure Downloading the Runtimes 7. You need an account to download CDK. If you have existing credentials, select the one you want to use. If you didn t, click Add to add your credentials. 27

32 Red Hat JBoss Developer Studio 11.3 Release Notes and Known Issues Figure Selecting Credentials 8. Click Next. Your credentials will be validated, and upon success, you must accept the license agreement. 28

33 CHAPTER 2. RELEASE NOTES Figure Accepting the License Agreement 9. Accept the license agreement and click Next. 29

34 Red Hat JBoss Developer Studio 11.3 Release Notes and Known Issues Figure Completing the Download Runtimes Task 10. Choose the folder where you want to install the runtime. Click Finish. The download of the runtime begins. You can see the progress on the Server Adapter wizard. 30

35 CHAPTER 2. RELEASE NOTES Figure Progress of the Download Runtimes Task 11. After the download is complete, you will notice that the Minishift Binary and Username fields are filled. 31

36 Red Hat JBoss Developer Studio 11.3 Release Notes and Known Issues Figure Populated Minishift Binary and Username Fields 12. Click Finish to create the server adapter. Note that if it is the first time that you have installed CDK, you must initialize the Server. In the Servers view, right-click the server and click Setup CDK. 32

37 CHAPTER 2. RELEASE NOTES Figure Initialize the CDK Server Related JIRA: JBIDE CDK Server Adapter Integrated Setup When starting a CDK server adapter, a setup procedure must be previously run. Initially, this must be run outside the IDE through the minishift setup-cdk command. In the previous milestone, this has been possible from the IDE through a new action from the Servers view. It is now integrated in the start phase of the server adapter. If the MINISHIFT_HOME folder associated with the CDK server adapter is detected as uninitialized, then the user is asked if the setup-cdk command should be run and if approved by the user, it will be run prior to the start command. Related JIRA: JBIDE

38 Red Hat JBoss Developer Studio 11.3 Release Notes and Known Issues 3.1. RESOLVED ISSUES CHAPTER 3. ISSUES To view information about resolved issues in this release of JBoss Developer Studio, see the Resolved Issues KNOWN ISSUES To view information about known issues in this release of JBoss Developer Studio, see the Known Issues. The following known issues are highlighted: JBIDE-20983: cannot use oracle service name in datasource creation JBIDE-19633: Not able to create 'non-bare' repository in JBDS 8.1. JBIDE-17176: Unable to browse and select PortletBridge runtime libraries in JPP 6 JBIDE-12957: Xhtml files appear garbled when it s reopened in the JBDS editor JBDS-3645: Installation of JBoss Developer Studio to a network drive fails JBDS-3470: Toolbars + Icons unusable on UHD screens JBDS-3069: Ungraceful shutdown results in multiple errors on startup JBDS-4442: Central page does not work on Fedora 26 if package webkitgtk3 is not installed JBIDE-25146: Eclipse annotation processing not enabled by default can result in errors 3.3. RED HAT JBOSS FUSE RELATED ISSUES Following is a list of issues for the DevStudio and JBoss Fuse integration: FUSETOOLS-2859: Provide automatic migration of dozer file when "Change Camel version" from version < 2.20 to version >=

39 CHAPTER 4. ADDITIONAL RESOURCES CHAPTER 4. ADDITIONAL RESOURCES JBoss Developer Studio 11.3 is available from a number of sources: To install JBoss Developer Studio 11.3, use the universal installer available from the Red Hat Customer Portal or from the Red Hat Developer Program. To install JBoss Developer Studio BYOE 11.3 in Eclipse Oxygen, use Eclipse Marketplace, the JBoss Developer Studio update site or the update.zip file available from the Red Hat Customer Portal. In all cases, for more information, see the Red Hat JBoss Developer Studio Installation Guide at the JBoss Developer Studio Documentation page. 35