Posts tagged with 'jbosstools'

The goal of the Diagram tab is to visualize the flowchart-like structure of batch jobs. Don’t bother editing the XML by hand and tracking down paths in your batch’s workflow. Instead, you can manipulate batch elements directly with your mouse.

Just select the proper objects from the palette, place them in the diagram and draw transitions among them. The editor visualizes all step, flow, split and decision elements, transitions using next attribute and next on elements and also terminating elements (fail, stop, end). If you need to edit elements nested inside a flow, just double-click its icon to switch the contents of the editor to the flow internals.

You also don’t need to reorder XML elements to set an element as a start. Just use Set as Start action.

The diagram is useful for displaying structures but sometimes we would like to different things like to assign a Java bean to a batchlet. That’s when the Properties View comes in handy. Its content is changed according the current selection in the diagram and it serves for filling in various form data.

Tip: Use Ctrl+Space to get content proposal.

The diagram editor is integrated with the tree-form editor and the XML text editor in the way that all changes are propagated immediately between these three views. Use any of the editor tabs and you’ll see the changes reflected in the other tabs.

The editor is aware of the batch nature of your project and provides content proposal. It helps to fill in names batch artifacts such as jobs or flows, specific Java classes (your subclasses of ItemReader ItemWriter etc.) or exception classes. You may refer to your beans also by their name defined by the @Named annotation.

Just download the latest 9 release of JBoss Developer Studio or 4.3 version of JBoss Tools to get started. To quickly create a new file, try e.g. the wizard for creating batch files by selecting File  New  Other  Batch  Batch Job XML File.

Enjoy using the editor and give us some feedback!

Tomáš Milata
@tomas_milata

The Integration Stack for JBoss Tools Developer Studio is a set of plugins for Eclipse that provides integration tooling for the following frameworks.

Updates have been made to the Business Process tooling, Fuse Tooling, Data Virtualization and SwitchYard. See the Integration Stack 8.0.2 Release Notes

The easiest way to install the Integratin Stack components is to install JBoss Developer Studio Integration Stack from the Eclipse Marketplace via Help > Eclipse Marketplace…​

For a complete set of Integration Stack installation instructions, see Integration Stack Installation Instructions

More to come…​

Paul Leacu.

To use this Beta, you must run Eclipse with Java 8.

You can still target development for old Java versions though. Yes, you can still target your Java 1.4 projects :)

We are doing this because certain components of Eclipse Mars now require Java 8 (especially Sapphire) and according to our usage stats, Java 8 will have gained majority this year.

But we have not made JBoss Tools dependent on Java 8 yet, since we want to get feedback from users on whether requiring Java 8 will be a problem.

Let us know on our forum, or contact Red Hat support if this will be a problem for you to use it.

JBoss Developer Studio comes with everything pre-bundled in its installer. Simply download it from our JBoss Products page and run it like this:

JBoss Tools or Bring-Your-Own-Eclipse (BYOE) JBoss Developer Studio require a bit more:

This release requires at least Eclipse 4.5 (Mars) but we recommend using the Eclipse 4.5 JEE Bundle since then you get most of the dependencies preinstalled. In case that page it not available check main eclipse download for the Mars release.

Once you have installed Eclipse, you can either find us on the Eclipse Marketplace under "JBoss Tools (Mars)" or "JBoss Developer Studio (Mars)".

For JBoss Tools, you can also use our update site directly if you are up for it.

Note: Integration Stack tooling will become available from JBoss Central at a later date.

The full details of what is new is available on this page. Some highlights below.

Let us know what you like/hate about the release and if you find issues, please open a ticket at our issue tracker.

Going from Beta1 to Beta2, we are focusing on reported issues and going for improving Docker, OpenShift, JavaScript and JavaEE related features.

Hope you enjoy it and remember…​

Have fun!

Max Rydahl Andersen
@maxandersen

The last transformation tooling we had in JBoss Tools leveraged Smooks to convert one format to another. This time we’re using the Dozer framework, which offers a great base for handling Java to Java transformations. Through various APIs, you can convert just about anything to a Java model these days and that gives us a good place to start.

With the addition of Fuse technologies (and some awesome developers), we gained some cool new toys in the tooling and a big part of that is the Camel Editor (i.e. the "Fuse Tooling Routes Editor"). The Fuse Transformation tooling builds on that and offers:

Though we’re in Tech Preview for now, we have good collection of functionality already and we’ll walk through some of that.

The new tooling appears in the JBoss Tools Integration Stack "Early Access" site, so be sure to keep up with that effort. (You can see Paul’s latest post here: "JBoss Tools Integration Stack - Luna integration tooling for BRMS/BPMS, Data Virt, SOA 5.x + Early Access Fuse and SwitchYard."

Keep up to date with JBoss Tools Integration Stack to ensure you have the latest version of the Transformation tooling.

I’m going to cheat a little and start with the "Starter" project that we have created for the Transformation project. It includes some sample data to demonstrate transforming from XML to JSON. It includes a sample Camel configuration as well (in either Spring or Blueprint form) that provides a route that takes a file and routes it to another. In this case, we’re going from a sales order in XML format (abc-order.xml) to a sales order in JSON format (xyz-order-schema.json). This is a common integration case where you have to migrate one format to another.

Why yes, I did! But I also said that we have ways to create Java models from other formats. And in this first wave of Transformation functionality we offer built-in conversion from XML (XML schemas or instance documents) and JSON (JSON schemas or instance documents) to help get you that far. plus some other, more open-ended capabilities we’ll talk about down the line, we will walk through each step of getting you from your sample data to a fully testable solution.

So let’s get started…​

There are three main ways to launch the New Transformation Wizard in Eclipse…​

Once you’ve launched the New Fuse Transformation Wizard, you are presented with a wizard page that looks something like the following.

Currently with the wizard we have the ability to transform to and from one of four different types:

Today we’re focused on converting from XML to JSON, so we’ll select those two types and click Next.

Since we selected XML as the Source Type on the Start page, we’ll see the "Source Type (XML)" page appear next. If we had selected another type, we’d see that page here.

In this case, we have an XML Schema document (abc-order.xml) that we want to transform from. So we’ll click on the Source File field’s "…​" button to browse for our file, select abc-order.xml, and click Next to continue. If you have a particularly complex schema, you may need to select from the root elements you wish to key on for the transformation.

Since we selected JSON as the Target Type on the Start page, we’ll see the "Target Type (JSON)" page appear next. If we had selected another type, we’d see that page here.

In this case, we have an JSON Schema document (xyz-order-schema.json) that we want to transform to. So we’ll click on the Target File field’s "…​" button to browse for our file, select xyz-order-schema.json, and click Finish to continue.

As soon as the wizard is done, you’ll notice two things.

For now, we’ll close our new Transformation and go back to the Camel route to finish hooking up the new endpoint.

When we select the Camel editor again, we notice that a new endpoint reference has been added to the canvas. We need to now hook that into our route so it happens between our source and target steps of this simple configuration.

The first thing we need to do is delete the existing link between the "src" and "target" elements of the route. You can click on it and hit the Delete key on your keyboard or right-click on the arrow and select "Remove." When it asks if you want to remove the element, click Yes.

Now we can wire up the endpoint.

So now we have a new Transformation endpoint that is wired into our Camel route.

Next time we’ll start doing the actual editing of the Transformation itself!

Thanks for reading!
Brian "Fitz" Fitzpatrick

The WTP platform includes a TCP/IP monitor as a standalone entity. You can use it manually, which I’ll explain now, but the real magic happens when integrated with our server adapters.

There are two primary pieces to the TCP/IP Monitor. First, there’s a preference page, where you can add port mappings and enable or disable monitoring on that port. Secondly, there’s a TCP/IP Monitor view.

So there we have it: A long-standing omission has finally been put in place. What’s more, other server adapters don’t integrate with this feature as completely as we do. If you were to run the same experiment on the Tomcat adapter, and execute the "Run As → Run on Server" action for a web project’s servlet or html file, the browser will still open up on port 8080, rather than the Local Port which can be used for monitoring. When targeting JBoss and WildFly servers, though, these actions behave as a user would expect and hope.

So get in there and monitor some traffic! Grab a nightly build from our downloads section, or just use our nightly update site directly:

Related JIRA: JBIDE-19755 - Implement ServerPort portion of wst.servertools API

Rob Stryker

This version of JBoss Tools targets Eclipse Mars 4.5 (M6).

We recommend using the Eclipse 4.5 JEE Bundle since then you get most of the dependencies preinstalled.

Once you have installed Eclipse, you use our update site directly:

Note: Marketplace entry and Integration Stack tooling will become available from JBoss Central at a later date.

We have included our incubation project at Eclipse that makes importing and opening of projects much easier than default Eclipse. No longer do you need to know or guess at which of many import wizards are the right one. With this you just use File  Import Project from Folder, point it to a folder and it will auto-detect the type of project, imports ann configure it as best as it can.

Once started it will recursively scan the selected folder and report which directories it found.

We included this incubation feature to get early feedback - please do give it a try and let us know if it works great or if we detected some projects "badly".

Our OpenShift integration now allow you to connect to OpenShift 3 in addition to the existing OpenShift 2 support.

Once connected you can browse the OpenShift/Kubernetes data for your application/projects.

Note: OpenShift v3 is not available from openshift.com to try at this point in time. If you want to try use it you can follow the instructions at OpenShift Origin sample app.

In Alpha 1 we introduced support for Java EE 7 batch specification and now extending this support with a wizard, content assist, linked navigation, searching and refactoring of Batch elements.

Details are in Batch Tools New and Noteworthy.

We’ve added native WildFly 9 runtime detection and server support. You no longer need to use the WildFly 8 adapter and detection will work correctly now.

When editing AngularJS single-page html (not templates) the html editor now communicates with the preview to provide content assist for angularjs expressions.

There is now a quickfix for marking custom HTML5 elements to be ignored in validation.

Note: this is not specific to JBoss Tools, it is built into Eclipse M6

With Alpha2 out we are heading towards a Beta1.

In Beta1 we are targeting including:

As always, ask/suggest away and we’ll keep you posted!

Have fun!

Max Rydahl Andersen
@maxandersen

JBoss Tools Integration Stack 4.2.1.Final / JBoss Developer Studio Integration Stack 8.0.1.GA

The Integration Stack for JBoss Tools Developer Studio is a set of plugins for Eclipse that provides integration tooling for the following frameworks.

Updates have been made to the Business Process tooling (BPMN2 Modeler), Fuse Tooling and SwitchYard. See the JBDSIS 8.0.1 Release Notes

JBoss Developer Studio comes with everything pre-bundled in its installer. Simply download it and install it like this:

If you have JBoss Developer Studio 8.0.0.GA already installed, just run:

JBoss Tools or JBoss Developer Studio Bring-Your-Own-Eclipse (BYOE) requires a bit more:

This release requires at least Eclipse 4.4 (Luna) but we recommend using the Eclipse Luna SR2 Java EE Bundle since then you get most of the dependencies preinstalled with Java EE Bundle and SR2 release includes some critical fixes.

Once you have installed Eclipse, you can either find us on Eclipse Marketplace under "JBoss Tools (Luna)" or "JBoss Developer Studio (Luna)".

For JBoss Tools you can also use our update site directly if you are up for it.

This release is update for Eclipse Luna and also includes some new features which we would like to highlight. You can see everything in the What’s New section for this release.

This version of JBoss Tools targets Eclipse Luna SR2. More stability. Less false positive JavaScript errors. And many other fixed bugs.

JBoss Developer Studio also includes an important feature patch for Eclipse Web Tools 3.6.3. That patch fixes Eclipse freezes for some JavaScript files.

If you are a FeedHenry user we’ve now added support for easy importing and running of your FeedHenry Cordova applications.

WildFly 8.2.0.GA archetypes are now available for the HTML5, JavaEE Web & EAR project wizards. They will be automatically enabled when you select a WildFly runtime in the project wizards.

For JBoss 7 and Wildfly installations, using hostnames with an IPv6 format often failed to connect, show webpages, or even verify the server’s state. Several changes have made this work as expected. With updated wildfly jars, management commands will execute without issue. In addition, our tools will now automatically recognize host names in an IPv6 pattern, and update your launch configuration’s various launch arguments to ensure that the server starts properly and with all expected flags set.

The Forge 2 runtime was upgraded to 2.15.2.Final. See the full release notes here.

There is also an improvement in Forge wizards which now render notes below the inputs (where available):

HTML validation in Eclipse Web Tools Luna has an annoying issue with custom HTML5 tags. It warns about any HTML tag name that is not mentioned in the HTML specification. We contributed a patch to Eclipse Mars which allows to disable those warnings for any particular tag name (or a tag name mask, e.g. <ion-*>). Though this was fixed in Eclipse Mars only we back ported this useful feature to JBoss Tools 4.2.3 which is based on Eclipse Luna SR2:

JavaSript file validation now respects ECMA5 keywords.

Tern.java and AngularJS Eclipse (available via JBoss Central - Early Access) has been upgraded to 0.8.2 version.

There is a bunch of new features which were introduced in 0.8.0 releases:

0.8.2 releases also include bug fixes for some critical issues which caused Eclipse to freeze.

On Linux Visual Page Editor can be opened in HTML5 mode for HTML files, where all HTML5 features are supported. Visual Page editor mode can be changed with dialog, which appears during HTML file opening or in Visual Page Editor Preferences.

Currently JBoss Tools and JBoss Developer Studio have some problems with supporting both HTML5 Visual Preview and JSF Visual Editor. It’s related to the outdated XULRunner which is used in JBoss Tools to provide visual editing feature for JSF pages. It has very limited HTML5 support and conflicts with other browsers which may be used for HTML5 preview. It’s time now to deprecate the visual part of XHTML and JSP Page editor. JBoss Developer Studio 8.1 and JBoss Tools 4.2.3 still include JSF Visual Editor but it will be removed in future releases.

This deprecation is only about the visual part of the XHTML/JSP Editor (Visual/Source and Preview tabs). The existing content assist, code navigation, wizards etc. related to JSF will still be present in the source editor.

We are now focusing on JBoss Developer Studio 9 and JBoss Tools 4.3 for Eclipse Mars. Alpha1 is already available and we are working on upcoming Alpha2.

Enjoy!

Alexey Kazakov

The Docker Explorer provides a wizard to establish a new connection to a Docker daemon. This wizard can detect default settings if the user’s machine runs Docker natively or in a VM using Boot2Docker. Both Unix sockets on Linux machines and the REST API on other OSes are detected and supported. The wizard also allows remote connections using custom settings.

The Docker Explorer itself is a tree view that handles multiple connections and provides users with quick overview of the existing images and containers.

Built-in filters can show/hide intermediate and 'dangling' images as well as stopped containers.

The Docker Images view lists all images in the Docker host selected in the Docker Explorer view. This view allows user to manage images, including:

A wizard lets the user input all the arguments to create a new container from an image. When the container is started, all the logs can be streamed into the Eclipse Console:

The Docker Containers view lets the user manage her containers. The view toolbar provides commands to start, stop, pause, unpause, display the logs and kill containers.

This view also provides a filter to show/hide stopped containers. Users can also attach an Eclipse console to a running Docker container to follow the logs and use the STDIN to interact with it.

We also integrate with the Eclipse Properties view to provide users with info and 'inspect' data about a selected container or image.

Roland Grunberg and Jeff Johnston from Red Hat started this project and are currently in the process of getting the code accepted to Eclipse.org as part of the Linux Tools project (even if the tooling also runs on other platforms), which explains why the code has not been made public yet.

Taking about code, we rely on the open source Docker client developed by Spotify to handle the low-level communication with the Docker daemons and I should thank the Spotify developers who maintain this library. They’ve been very kind to quickly review and merge the pull requests that we’ve submitted and it’s been a pleasure to contribute to their project. Open source collaboration FTW :-)

There is still some work and the screenshots showed above may still evolve as we add more features, but we hope that this blog entry will give you a taste of what’s coming soon in Eclipse with regards to Docker tooling.

While the code will be hosted in Linux Tools project at Eclipse.org, we intend to also ship it as part of JBoss Developer Studio 9 and JBoss Tools 4.3 later this year.

We also created a JIRA component to track this work-in-progress in the scope of JBoss Tools, including some issues with mockups.

Beyond this basic Docker tooling we are looking at integrating launching servers and even native CDT builds on docker containers, but this will be the subject of future posts on this blog ;-)

As usual, feel free to provide us with feedback on our forum, on JIRA or on IRC. Questions, comments and suggestions are always welcome!

Stay tuned!

/Xavier
@xcoulon

Red Hat JBoss Developer Studio comes with everything pre-bundled in its installer. Simply download it and install it like this:

JBoss Tools or JBoss Developer Studio Bring-Your-Own-Eclipse (BYOE) requires a bit more:

This release requires at least Eclipse 4.4 (Luna) but we recommend using the Eclipse Luna SR2 Java EE Bundle since then you get most of the dependencies preinstalled with Java EE Bundle and SR2 release includes some critical fixes.

Once you have installed or if you have JBoss Tools 4.2.x already installed, you can use our update site directly for JBoss Tools:

And for JBoss Developer Studio Bring-Your-Own-Eclipse:

Note: JBoss Tools 4.2.3 and JBoss Developer Studio 8.1.0 will become available in Marketplace only for Final releases at early April

We are getting close to the final release. So, we focused on bug fixing in this release.

Besides bug fixes, the Forge 2 runtime was upgraded to 2.15.1.Final. See the release notes here.

There is also an improvement in Forge wizards which now render notes below the inputs (where available):

It’s worth mentioning that the Forge 2.15.1 release has an annoying bug which prevents addons creation. The upcoming JBoss Developer Studio 8.1.0.Final will include the fixed Forge 2.15.2.Final (has been released today).

The next stop is JBoss Tools 4.2.3.Final and JBoss Developer Studio 8.1.0.Final which are going to be released in two weeks.

Enjoy!

Alexey Kazakov