Lightweight Dialogs in e4 & JavaFX

by Tom Schindl at April 23, 2015 02:25 PM

I’ve just checked in the initial bits to use lightweight dialogs in your e4 + JavaFX applications. You can see it in action in the short video from below

Useage is fairly simple. First you need to have dialog implementation like this:

static class OpenProjectDialogImpl extends TitleAreaDialog {
  private ListView<Project> list;
  private final CommandService cmdService;

  @Inject
  public OpenProjectDialogImpl(Workbench workbench, 
    CommandService cmdService, @Service List<ProjectService> projectServiceList) {

    super("Open project", 
      "Open project", "Open an existing project");
    this.cmdService = cmdService;
    addDefaultButtons();
    setMaxWidth(500);
    setMaxHeight(500);
    setId("open-project-dialog");
		
    list = new ListView<>();
    list.setMinWidth(600);
    list.setCellFactory(v -> 
      new SimpleListCell<Project>( 
        p -> labelExtractor(p, projectServiceList), 
        p -> cssProvider(p,projectServiceList)));
    list.setItems(FXCollections.observableArrayList(
      workbench.getProjectList()));
    setClientArea(list);
  }
	
  @Override
  protected void handleOk() {
    if( list.getSelectionModel().getSelectedItem() != null ) {
      cmdService.execute("org.eclipse.fx.code.compensator.app.command.openproject", Collections.singletonMap("projectId", list.getSelectionModel().getSelectedItem().getProjectId()));
      super.handleOk();	
    }
  }
}

and displaying it is nothing more than:

public class OpenProjectDialog {
  @Execute
  public void open(LightWeightDialogService dialogService) {
    dialogService.openDialog(OpenProjectDialogImpl.class, ModalityScope.WINDOW);
  }
}

As you can see in the video you can choose how the dialog is opened & closed. This is done through an OSGi-Service of type LightweightDialogTransitionService:

@Component
public class FadeDialogTranstionServiceImpl extends FadeDialogTranstionService implements LightweightDialogTransitionService {
  @Override
  protected void configureFadeIn(FadeTransition transition) {
    super.configureFadeIn(transition);
    transition.setInterpolator(Interpolator.EASE_OUT);
  }
	
  @Override
  protected void configureFadeOut(FadeTransition transition) {
    super.configureFadeOut(transition);
    transition.setInterpolator(Interpolator.EASE_OUT);
  }
}


by Tom Schindl at April 23, 2015 02:25 PM

Developing for Cloud Foundry

April 23, 2015 02:07 PM

We are pleased to have a series of articles describing how developers can use Eclipse and Orion for developing Cloud Foundry applications.

April 23, 2015 02:07 PM

Font Icons for Eclipse Scout

by Matthias Zimmermann at April 23, 2015 09:08 AM

Today, web pages and web applications start to rely more and more on font icons. As clean and modern icons can help an application to get a professional look and feel we went through the little exercise to demonstrate how to use font icons in Eclipse Scout applications.

One of the most prominently used icon font on many web pages is Font Awesome. As the font contains hundreds of icons that are free to use even in commercial applications, it is ideally suited for demonstration purposes as well as productive use.

font_awesome_homepage

The reminder of the article describes the usage of such fonts for icons with Eclipse Scout.

To demonstrate the usage we added an icons and font icons form to the Scout Widget Application.

demoapp_fonticon

In the text below we will first talk about the general usage of icons in Scout application, and discuss how icons are provided to the application through icon provider services. Then the font icon provider services is introduced that allows to create Scout icons for individual characters from any true type font files.

How To Use Icons in Scout

Icons can be used for a number of UI components in Scout applications. They may be used for buttons, image fields, for smart fields entries, tree nodes and for table rows. To identify individual icons, its icon name/id can be used. The simplest way to figure out how to use icons in Scout applications is to follow the code of the Scout widget application.

For a concrete example we will look at the implementation for the button with the white arrow pointing to the right that is implemented in the icons form of the Scout widget application.

button_with_arrow

 

To find the corresponding code in the widget application, open the IconsForm and drill down to the ExamplesBox group box and locate the IconButton class. In method getConfiguredIconId the desired icon is specified as shown below. 

  @Order(4000.0)
  public class IconButton extends AbstractButton {
    ...

    @Override
    protected String getConfiguredIconId() {
      return AbstractIcons.WizardNextButton;
    }

    ....
  }

From this example we can see that a few icons come out of the box with the Scout framework. As every application has its own special needs, additional application specific icons may be located in the client plugin of the application. In the default case the corresponding image files may be placed in folder resources/icons of the client plugin. In the example of the Scout widget application the icon “star_yellow” is backed by image file star_yellow.png in the icon resource folder. This represents the simplest way to add your own icons to your application. Just put your icon image files into the folder resources/icons of the client plugin as in the case of the yellow_star icon.

However, designing good looking icons is time consuming and to get started quickly having a large amount of icons out of the box would be helpful. To take advantage of the fact that with the Font Awesome toolkit such a collection of high quality icons is available in the public domain, we can also write a specific icon provider that consumes the available icons from the Fontawesome true type font file at runtime.

The Font Icon Provider Service

Before we discuss the font icon provider service let us look at the general concept of icon provider service of the Scout framework. In Scout, icons are provided to the application through icon provider services. When a UI component needs to display an icon specified by its name, the Scout framework checks with the registered icon provider services to access the necessary image content.

At runtime, the icon name is fed into method getIconSpec of the first available service that implements the IIconProviderService interface. If the method returns null, the framework consults the next icon provider. This mechanism allows for the implementation of application specific icon provider services. There is one additional thing. To avoid the repeated generation of the image content, generated Icons are cached by the Scout framework. Instead of asking the icon provider services to create the content every time an icon is used, the framework first checks its cache, if an icon is already available from the cache, it will directly use this cached icon.

By writing a specific FontIconProviderService that converts characters from a true type font to Scout icons on the fly, font icons can be used along the traditional icons. To use font icons in the demo application only a few things are needed:

  • The font’s true type file (e.g. fontawesome-webfont.ttf) is located in folder resources/fonts of the client plugin
  • The alias information for the needed icons is specified in the icons.properties file (in folder resources/fonts)
  • The FontIconProvierService itself and its registration in the client’s plugin.xml

At startup of the FontIconProviderService, method initializeFonts is called through method initializeService that then loads the available true type fonts and properties file mentioned above. Using this information the icon provider service then returns the created font icons in method getIconSpec. The icon alias (IconId in the screenshot above) defined in the icons.properties file can either be used on its own or amended with various additional attributes:

  • Color (icon color, or icon background color if a background type is selected)
  • Size (true type font characters may be scaled to arbitrary sizes)
  • Background (to create inverted icons with a square or round background image)

In the example shown in the screenshot above, the icon specification is encoded into the string font:plane!#FAA635!128;fontawesome-webfont. This results in the search of alias “plane;fontawesome-webfont” in the properties file leading to the font’s character f072 that is then scaled to 128 pixels and colored using #FAA635.

To play around with the available options click on button “Sample Content” in the icons form of the widget demo application. There, you can change the icon id, the color, size and the background shape. When you switch the font from “fontawesome-webfont” to “cour”, you can also try to create an icon from a single letter (e.g. with the icon name “font:X!128;cour”).

Conclusion

In this post we have provided a quick introduction to the usage of icons in Scout applications and demonstrated how to use font icons in your own Scout applications. Using the provided FontIconProviderService you can now either use the discussed Fontawesome or use your own true type font files to extract font icons for your applications.

Project HomeForumWikiTwitter


by Matthias Zimmermann at April 23, 2015 09:08 AM

J2V8 2.2 New and Noteworthy

by Ian Bull at April 22, 2015 10:26 PM

I’m happy to announce the availability of J2V8 2.2 (2.2.1 actually). This release adds two important features: 1) Typed Arrays and 2) 64 Bit Windows support.

Typed Arrays

In Javascript, most arrays are untyped. That is, you can create an array and add anything to it.

var myStuff = [];
myStuff[0] = 42;
myStuff[1] = true;
myStuff[2] = "Strings";

A  few years ago, the Javascript community realized the need for a more efficient mechanism for working with binary data in WebGL. The result of this work were Typed Arrays. Typed Arrays are a continuous chunk of memory with a typed view onto it. The memory is managed by the underlying engine and they perform a lot better than regular Javascript arrays.

var buffer = new ArrayBuffer(256);
var i32 = new Int32Array(buffer);
i32[0] = 1;
i32[1] = 3;
i32[2] = i32[0] + i32[1];

In this example, an array buffer of 256 bytes is allocated. A view, rendering the data as an array of 32bit integers, is then projected onto that buffer. Because the memory is continuous and the types are known, the operations (such as add in this case) perform much faster.

J2V8 2.2 supports the creation of Typed Arrays. You can even access the contents of the arrays, in bulk, from Java using the getIntsMethod (getDoubles and getBoolean for doubles and booleans).

V8 v8 = V8.createV8Runtime();
V8Array result = v8.executeArrayScript("var buffer = new ArrayBuffer(256);\n"
 + "var i32 = new Int32Array(buffer);\n"
 + "i32[0] = 1;\n"
 + "i32[1] = 3;\n"
 + "i32[2] = i32[0] + i32[1];\n"
 + "i32;");
int[] ints = result.getInts(0, 3);
System.out.println("Result: " + ints[0] + ", " + ints[1] + ", " + ints[2]);
result.release();
v8.release();

64 Bit Windows Support

J2V8 now supports 64 bit Windows. The binaries have pushed to Maven Central and can be consumed using the following dependency.

<dependency>
  <groupId>com.eclipsesource.j2v8</groupId>
  <artifactId>j2v8_win32_x86_64</artifactId>
  <version>2.2.1</version>
  <scope>compile</scope>
</dependency>

For more news about J2V8, follow me on Twitter.


TwitterGoogle+LinkedInFacebook

Leave a Comment. Tagged with j2v8, j2v8


by Ian Bull at April 22, 2015 10:26 PM

Screenshot of the Week: Git Repositories View

by waynebeaton at April 22, 2015 02:40 PM

The Git Repositories view (which I tend to add to whatever perspective I’m working in) provides pretty much one-stop-shopping for most of my repository activity needs.

The Git Repositories View in Eclipse Mars

The Git Repositories View in Eclipse Mars

In this screenshot, you can see a handful of local branches that I obviously need to spend a few minutes cleaning up, and some stashed commits. Direct access to tags, references, and remotes is also provided. You can also work directly with files in the working directory if you opt to not create a project in the workspace.

I generally don’t tweak the default configuration of any software (I’m lazy that way), but I find that in Eclipse I’m starting to move the perspective launcher down to the bottom left of the window, turn the tool bar off (though not in this screenshot), and clear out views from the right side of the window (to make more room for the editor). What are your favourite tweaks?



by waynebeaton at April 22, 2015 02:40 PM

Setting profiles in the preferences dialog

by eselmeister at April 22, 2015 08:45 AM

I wondered if it’s possible to allow users to work with different profile settings. That would be beneficial, cause users then don’t have to remember different plug-in settings for various analytical scenarios. Eclipse offers to export/import *.epf files, hence there should be a way to automate this. Here’s the solution:

Profiles

The preference service allows to export the currently used preferences:

public static void exportProfile(File file, IPreferenceFilter[] preferenceFilters) throws FileNotFoundException, CoreException {

	FileOutputStream fileOutputStream = new FileOutputStream(file);
	IPreferencesService preferencesService = Platform.getPreferencesService();
	preferencesService.exportPreferences(preferencesService.getRootNode(), preferenceFilters, fileOutputStream);
}

Importing stored preferences works similarly:

public static IStatus importProfile(File file) throws FileNotFoundException, CoreException {

	FileInputStream fileInputStream = new FileInputStream(file);
	IPreferencesService preferencesService = Platform.getPreferencesService();
	return preferencesService.importPreferences(fileInputStream);
}

It depends on you where to store the preference profiles. There’s only a small drawback when loading a profile within the preferences dialog. All pages are displaying the old and not updated profile values. Hence, the dialog needs to be restarted. This can be automated too from within a page.

IPreferencePageContainer preferencePageContainer = getContainer();
if(preferencePageContainer instanceof PreferenceDialog) {
	PreferenceDialog preferenceDialog = (PreferenceDialog)preferencePageContainer;
	preferenceDialog.close();
	preferenceDialog = PreferencesUtil.createPreferenceDialogOn(null, null, null, null);
	preferenceDialog.open();
}

The more better it would be reload all page values without re-opening the preference dialog. But I didn’t find a way how to do it. Anyhow, it works so far.


by eselmeister at April 22, 2015 08:45 AM

Making the Text Editor to be the Default One for All Unknown Files in Eclipse

by Kaloyan Raev (noreply@blogger.com) at April 22, 2015 06:16 AM

Eclipse users usually work with many different file types. Some of the file types may be opened by default in an external editor instead of in the Eclipse workbench. This happens if Eclipse has no editor available to handle that particular file type, but there is one installed in the operating system. In such case Eclipse assumes that it is better for the user to have the file opened in the external system editor.

Lots of users are quite annoyed by this behavior, especially when it comes to text-based files. They would prefer to have the file opened in the plain text editor of Eclipse instead of switching the context to the external program. Unfortunately, there is no easy way to change this in the preference settings. It's possible to associate a specific file extension with the plain text editor, but this must be done separately for every file extensions. There is no way to say "all text files of unknown type should open in the text editor".

Here comes the Default Text Editor plugin. It takes advantage of the Editor Association Override extension point introduced in Eclipse 3.8. When the plugin is installed it will change the default behavior of Eclipse and will opened all text files of unknown type in the plain text editor. Binary files like images may still be opened in an external system editor. As simple as that.

The plugin is available on the Eclipse Marketplace. It can also be installed through an update site. More info is available on the GitHub project.

by Kaloyan Raev (noreply@blogger.com) at April 22, 2015 06:16 AM

$150 Bug Bounty for Fixing a Dark Theme Issue

by Kaloyan Raev (noreply@blogger.com) at April 21, 2015 06:54 PM

Zend Studio is an IDE based on the Eclipse Platform. The dark theme is an important feature and is very popular among PHP developers. The most annoying issue with the dark theme, we have at the moment, is that the expand/collapse toggle in trees is almost invisible on Windows, because it seems to be unaffected by the dark theme coloring. See Eclipse bug 434201 for details.



We decided to put some money on the table with the hope that someone will step in and fix this bug. This will benefit not only Zend Studio users, but all Windows users in the Eclipse ecosystem who want to use the dark theme.

We created a $150 bug bounty on the FreedomSponsors crowd-funding platform. Follow this link to open the sponsored issue. Since this is a crowd-funding platform, anyone else who is ready to give some money for resolving this issue is welcome to do it, so the offer becomes more attractive.

UPDATE. The bug has been fixed within days and it will be delivered with the Mars M7 milestone. Thanks to Fabio Zadrozny for his great work. Kudos to Lars Vogel for adding $100 more to the bounty.

by Kaloyan Raev (noreply@blogger.com) at April 21, 2015 06:54 PM

Gendoc v0.5 released

by Tristan FAURE (noreply@blogger.com) at April 21, 2015 11:24 AM

Gendoc is officially an eclipse project and first official release is now available.
Gendoc is a template based technology allowing generation of OpenXML (Word) and Open Document (OpenOffice, LibreOffice) documents from EMF Models/XML using Acceleo language. Gendoc is currently industrially used in several critical systems company (space, avionics).

To start working with Gendoc and Luna please find update site in downloads section : http://www.eclipse.org/gendoc/downloads/download.php

Documentation and tutorials are available here : http://www.eclipse.org/gendoc/documentation/documentation.php

For any information or questions feel free to use links referenced on community section.


by Tristan FAURE (noreply@blogger.com) at April 21, 2015 11:24 AM

SWT Development, a comprehensive guide. (SWT -> Gtk)

by Leo Ufimtsev at April 20, 2015 07:18 PM

I typed up a comprehensive guide on SWT Development (Gtk side).

img_2015_04_20__11_15_12

It covers:
– SWT Develeper Setup.

– Navigating SWT code base.

– Building SO images to run latest master.

– Adding functions to OS.java.

– Compining and testing various Gtk Versions.

– Diagrams for complex workflows and detailed explanations.

Link: http://leoufimtsev.github.io./org/swt-dev.html

Please feel free to post questions & feedback into comments.



by Leo Ufimtsev at April 20, 2015 07:18 PM

Shared blog for EclipseSource Munich

by Maximilian Koegel at April 20, 2015 04:39 PM

To make it simpler for you to follow our blog posts from EclipseSource Munich we will now use a joint blog for all topics related to our work in Munich. This means there will be less posts that appear on my blog since I will post many things on the new Blog. All posts on the new blog are announced on the Twitter Account and Google+ page, see details below:

New Blog: http://eclipsesource.com/blogs/author/helmingkoegel

Twitter: https://twitter.com/EclipseSourceM

Google+: https://plus.google.com/105940428433807258305/posts

See you on the new blog!

 Shared blog for EclipseSource Munich


TwitterGoogle+LinkedInFacebook

Leave a Comment. Tagged with emf, modeling, Munich, emf, modeling, Munich


by Maximilian Koegel at April 20, 2015 04:39 PM

Andmore 0.5-M1 Released

by kingargyle at April 20, 2015 02:05 PM

Screen Shot 2015-04-19 at 4.44.52 PM

Android development using eclipse has taken a step forward today.  The first stable milestone release is ready for you, the user community to kick the tires, and start to use for your development.  Full details can be found in the New and Noteworthy section for the release notes.

There is a p2 site for your installation needs, and it is recommended that you not install both Android Developer Tools and Andmore into the same IDE.

http://download.eclipse.org/andmore/milestone/0.5-M1/

Add the above url to your available software sites.

Andmore contains all the functionality and features of Android Developer Tools, plus a lot more.    Also, thanks to Ricardo Gladwell for updating the m2e-android plugin to support Andmore.  This means that if you are using maven already, you can continue to do so with Andmore to continue developing Android applications and manage your dependencies.  The p2 site for maven support is:

http://rgladwell.github.io/m2e-android/updates/master/

So what about Gradel support and the the android gradle plugin?  Right now this is targeted for 0.5-M2.   There is a lot of stuff that needs to occur in order for this to happen.  For one thing, AAR support is necessary.   We also need to look into what extension points that the Buildship project will offer.  Will Andmore need to provide any extension points to allow Maven and Gradel to have more control over the build process?

Limitations with the current Andmore release:

  • No AAR support
  • No Gradel support
  • Android API 22 has limited support.  The only piece that may give you an error message is the GUI Layout editor.  If this happens change the API level in the editor from 22 to 21 or lower.

There is plenty to do yet, and the project is very open to contributions from the community.  If you would like to help out with any of the remaining work, do not hesitate to fork the repo on Github, and submit a pull request.   Andmore will be what the community makes it.  Bugs and Feature requests can be opened at:

https://bugs.eclipse.org/bugs/enter_bug.cgi?product=andmore



by kingargyle at April 20, 2015 02:05 PM

Eclipse IoT Breakfast in Madrid on May 21

by Benjamin Cabé at April 20, 2015 12:44 PM

We are happy to co-organize an IoT breakfast together with Eclipse Foundation member SQS, on May 21 in Madrid (Ayre Gran Hotel Colón).

I’ve already been asked “An IoT breakfast? What’s that!?” – well, think of it as your regular meetup, only we’re doing it in the morning rather than in the late afternoon :-)

The agenda will be as follows:

  • What’s new about Eclipse: the IDE and beyond! by Gaël Blondelle, Director of European Ecosystem Development at the Eclipse Foundation.
  • Open Source for the Internet of Things by Benjamin Cabé, IoT Evangelist at the Eclipse Foundation
  • Testing the IoT. Challenges, Approaches and Tools by Itziar Ormaetxea, SQS TestLab Manager

The event is free but you need to register. We have limited space so please don’t wait. I hope to see you there!


by Benjamin Cabé at April 20, 2015 12:44 PM

Meet the Individuals Responsible for Tasktop’s Customer Journey

by Neelan Choksi at April 17, 2015 04:15 PM

As part of our growth at Tasktop, it has been critical that we add in key leaders to sustain and facilitate that growth into the future. I’m thrilled to be talking about the new group of sales leaders we have at Tasktop and feel privileged to be working with this outstanding group. Tasktop now has new sales leaders for Americas West, East, Central as well as a new leader for pre-sales.

Jamie Wetzel has been promoted from an individual contributor role to lead Americas West. I think I am most proud of this as I love when we promote from within. Now in his 5th year with the company, Jamie has proven throughout his years at Tasktop that he’s been management material by embodying our culture and frankly being a leader before ever being given the title. I think Jamie has single-handedly attempted to enable every person who comes to Tasktop, and I am glad that we are able to reward Jamie with this promotion. Truth be told, I think the company is getting the larger reward.

We recently hired John Kapral to lead our Americas East and Central regions. I love Kap’s experience, having started his career in inside sales and working his way up into sales management in a diverse enterprise software career that has spanned such stalwarts (and in some cases Tasktop partners) as Splunk, CA, Symantec, BMC and CSC. In just over 2 quarters at Tasktop, I am already finding that I am relying on Kap’s experience and expertise with sales management and can see marked improvements in Tasktop’s Go to Market process and sales execution.

I am also thrilled that this past summer, we hired Maury Cupitt to lead our pre-sales engineers. Maury has been involved with pre-sales engineering for much of his career, which included working for Netscape, AvantGo, Wily, CA, and Blue Stripe. One of my favorite things about Maury is that he has brought back and instituted the ALM Architecture diagrams to be part of our pre-sales and post-sales processes – something that was so critical in our early days, helping us plot and flow our customers’ ALM tools and the information that needed to be passed between them.

Lance Knight has been given the tremendous responsibility of managing our post-sales activities as VP of Customer Success. His team is responsible for getting our customers deployed, delivering product-related services for customers, providing post-sales support, conducting customer health checks, teaching our customers through our extremely well-reviewed training courses, and driving our knowledge management assets. Like everything Lance touches, he has embraced the role of Customer Success. Lance likes to remind us that his job title is a bit of a misnomer since we all are responsible for Customer Success. Regardless, I feel very fortunate to have Lance leading this team as Tasktop continues to grow.

Yes, we have great innovative products. But working for a company is about the people. And I am proud to be working at Tasktop because we have an outstanding staff of intelligent, hardworking, self-motivated team members who love to win. If you read this and are excited by what you are hearing and are interested in exploring career options at Tasktop, check out our careers pages or contact us.


by Neelan Choksi at April 17, 2015 04:15 PM

Buildship on the mission to Mars

by Simon Scholz at April 17, 2015 03:00 PM

2286865364_900e1fe74e_z

Gradleware decided to implement their own tooling solution for building project within the Eclipse IDE and the Buildship project was born.

Selection_103

Since march there are currently 123 commits on the master branch of the GitHub project, which can be found here: https://github.com/eclipse/buildship

We from the vogella company will be working together with Gradleware and hopefully many other contributors as well.

Therefore we started a new tutorial concerning the Buildship project, which will be constantly updated, when new features will be available. See http://www.vogella.com/tutorials/EclipseGradle/article.html
Detailed information can also be found on GitHub: https://github.com/eclipse/buildship

Here is a little impression for you:

gradle_blog_teaser

As I already “println” in the build script, please help us by contributing to the Buildship project. So make your hands dirty, read the tutorial and give the Buildship project a try.

I’d also like to quote Wayne Beaton (Blog entry concerning Buildship):

Great Fixes for Buildship will qualify for the Great Fixes for Mars Skills Competition!

 

 


by Simon Scholz at April 17, 2015 03:00 PM

JBoss Tools Integration Stack - Luna integration tooling for BRMS/BPMS, Data Virt, SOA 5.x + Early Access Fuse and SwitchYard

by pleacu at April 17, 2015 01:19 PM

The Luna tooling train continues! - Adding JBoss Business Process and Rules development tooling to JBoss Data Virtualization and the SOA 5.x suite plus updates to the early access components.

jbosstools jbdevstudio blog header

What’s an Integration Stack?

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.

JBoss Business Process and Rules Development

  • BPEL Designer - Orchestrating your business processes.

  • BPMN2 Modeler - A graphical modeling tool which allows creation and editing of Business Process Modeling Notation diagrams using graphiti.

  • Drools - A Business Logic integration Platform which provides a unified and integrated platform for Rules, Workflow and Event Processing.

  • jBPM - A flexible Business Process Management (BPM) suite.

JBoss Data Virtualization Development

  • Modeshape - A distributed, hierarchical, transactional and consistent data store with support for queries, full-text search, events, versioning, references, and flexible and dynamic schemas. It is very fast, highly available, extremely scalable, and it is 100% open source.

  • Teiid Designer - A visual tool that enables rapid, model-driven definition, integration, management and testing of data services without programming using the Teiid runtime framework.

JBoss Integration and SOA Development

Note - the SOA Development tooling category has both released and early access components. Consequently, you will see it in both the release install dialog and the early access install dialog.

  • All of the Business Process and Rules Development plugins, plus…​

  • Fuse Apache Camel Tooling - A graphical tool for integrating software components that works with Apache ServiceMix, Apache ActiveMQ, Apache Camel and the FuseSource distributions.

  • SwitchYard - A lightweight service delivery framework providing full lifecycle support for developing, deploying, and managing service-oriented applications.

SOA 5.x Development

  • JBoss ESB - An enterprise service bus for connecting enterprise applications and services.

  • jBPM3 - A flexible Business Process Management (BPM) Suite - JBoss Enterprise SOA Platform 5.3.x compatible version.

All of these components have been verified to work with the same dependencies as JBoss Tools 4.2 and Developer Studio 8.

What’s Been Updated?

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

Released Tooling Highlights

BPMN2 Modeler Highlights

Early Access Tooling Highlights

Fuse Tooling Highlights

  • FUSETOOLS-1285: Broken parsing and missing configuration of exchange pattern for ToDefiniton endpoint

  • FUSETOOLS-1271: adding component connectors via context menu broken

  • FUSETOOLS-1269: Node Context Menu>Add option does not include the Components drawer items

  • FUSETOOLS-1268: Cannot view or edit file node in Properties editor after dragging a Filesystem component onto the canvas

  • FUSETOOLS-1267: Properties editor for File endpoint converts relative paths to absolute paths so files are not read

  • FUSETOOLS-1264: JMX Node in servers view doesn’t work if server has secured JMX access via credentials

  • FUSETOOLS-1261: Move connection between components cause problem

  • FUSETOOLS-1260: Cannot run Fuse server with alternate JRE

  • FUSETOOLS-1250: The IDE slows down when a fuse project is deployed

  • FUSETOOLS-1248: Debugger step over resets changed variable value and continues along original path

  • FUSETOOLS-1246: New Server Wizard bug with JMX Bundles plugin only

  • FUSETOOLS-1218: Cryptic error message displayed when trying to connect to Fuse 6.2 server

  • FUSETOOLS-1214: Run Configurations dialog shows launch config types for server adapters for Karaf, SMX, Fuse and Fabric8 which partially don’t work

  • FUSETOOLS-1211: Adding another route to a Fuse Project doesn’t work properly

  • FUSETOOLS-1173: Servers have too many jars on launching classpath

  • FUSETOOLS-1158: fix ugly title when debugging

  • FUSETOOLS-1148: Exception when browsing a BrokerNode in JMX View

  • FUSETOOLS-1138: NPE in karaf server core support after removing a deployed project

  • FUSETOOLS-1123: context id is removed on save

  • FUSETOOLS-1100: New Fuse project does not have properly set-up build-path

  • FUSETOOLS-1085: An endpoint is lost after saving

  • FUSETOOLS-1076: New Server Runtime Wizard - Finish button error

Also see Lars Heinemann’s Blog for more Fuse Tooling insights.

SwitchYard Highlights

The JBoss Tools website features tab

Don’t miss the Features tab for up to date information on your favorite Integration Stack components.

Installation

If you already have JBDSIS 8.0.0 installed…​

Simply start jbdevstudio or eclipse-with-jbds, then:

Select Help > Check for Updates

Select the components you’d like to install from the available updates.

If you’d like a fresh install…​

To install the Integration Stack tools, first install JBoss Developer Studio from the all-in-one installer, bundled and configured out of the box with everything you need to get started. Alternatively, if you already have eclipse-jee-luna installed, you can install JBoss Developer Studio or JBoss Tools from the Eclipse Marketplace via Help > Eclipse Marketplace…​

Eclipse Marketplace - JBDS

Once Developer Studio is installed, restart Eclipse and select the Software/Update tab in the JBoss Central view. The current 8.0.1.GA integration stack is available automatically with the released JBoss Data Virtualization Development tooling. The remainder of the integration tooling is available as Early Access so you must check the Enable Early Access checkbox in the installer window in order to install.

JBoss Central - JBoss Developer Studio Integration Stack
JBoss Central Early Access - JBoss Developer Studio Integration Stack

The standard p2 installer is available for JBoss Developer Studio Integration Stack. Simply start jbdevstudio or eclipse-with-jbds, then:

 Help > Install New Software...
       Add...
       - use this for &aposLocation:&apos for the production integration stack:
         https://devstudio.redhat.com/updates/8.0/integration-stack/
      
       - use this for &aposLocation:&apos for the early-access-components integration stack:
         https://devstudio.redhat.com/updates/8.0/integration-stack/earlyaccess/

The community JBoss Tools Integration Stack installation is easy as well. If you already have eclipse-jee-luna installed, install JBoss Tools from the Eclipse Marketplace via Help > Eclipse Marketplace…​

Eclipse Marketplace - JBoss Tools

Once JBoss Tools is installed, restart Eclipse and select the Software/Update tab in the JBoss Central view. The current 4.2.1.Final integration stack is available automatically with the released tooling. In a manner similar to devstudio, the remainder of the integration tooling is available as "Early Access" so you must check the "Enable Early Access" checkbox in the installer window in order to install.

Select the items you’d like to install:

JBoss Central Early Access - JBoss Tools Integration Stack

The standard p2 installer is available for JBoss Tools Integration Stack. Simply start eclipse-with-jbt, then:

 Help > Install New Software...
       Add...
       - use this for &aposLocation:&apos for the released-components integration stack:
         https://devstudio.redhat.com/updates/8.0/integration-stack/
      
       - use this for &aposLocation:&apos for the early access integration stack:
         https://devstudio.redhat.com/updates/8.0/integration-stack/earlyaccess/

Note: If you installed into your own Eclipse you should bump up the launch resource parameters:

--launcher.XXMaxPermSize 256m --launcher.appendVmargs -vmargs -Dosgi.requiredJavaVersion=1.6 -XX:MaxPermSize=256m -Xms512m -Xmx1024m

Give it a try!

Paul Leacu.


by pleacu at April 17, 2015 01:19 PM

Adding Actions to ToolBar of RCP

by Its_Me_Malai (noreply@blogger.com) at April 17, 2015 01:00 PM


Adding an Action to the ToolBar of an Eclipse Application or RCP. Doesnt that sound really easy. We just need to open up the WorkbenchActionBarAdvisor.java in the application plugin we just build and overried the fillCoolBar(). Like how we write code into fillMenuBar() I would expect to just take the coolBar object and add the action that was created in the makeActions to the coolBar.


But surprisingly that doesnt work. I was amazed and had to reach out to google to figure out why wasnt it working. Then someone pointed that only a toolbarcontributionitem can be added to the toolbar and recommended to look at the Mail RCP that is generated thru the PDE Templates for further information.

I did that out of curiosity and found this code which works.

Then I also understood the background of why I need to create a toolbar in org.eclipse.ui.menus before I can show something on the toolbar.

by Its_Me_Malai (noreply@blogger.com) at April 17, 2015 01:00 PM

Interview with InfoQ on the Internet of Things at Eclipse

by Benjamin Cabé at April 16, 2015 03:21 PM

Benjamin-Cabe

At EclipseCon 2015, I spoke with Alex Blewitt from InfoQ, and gave an update on the cool stuff happening at Eclipse IoT. It is hard to believe that it is only two years since my last interview with Alex – so many new projects and companies involved today!

Check out the interview here.


by Benjamin Cabé at April 16, 2015 03:21 PM

Andmore 0.5-M1 RC2

by kingargyle at April 16, 2015 01:55 PM

Release Candidate 2 is available for smoke testing.   This is mainly some spit and polish to remove the Andmore name from the menus and views, and replace them with more generic labels where it makes sense.

http://download.eclipse.org/andmore/milestone/0.5-M1/

Just add the above to your Install Software, and select the Andmore features to install.  Note that if you have existing ADT projects that you want to work with Andmore, you will need to Configure those to work with the new tooling.  To do so select a project, Configure->Convert ADT project.

If no new big show stoppers are reported by next week, we will do a formal 0.5-M1 announcement with complete change log.



by kingargyle at April 16, 2015 01:55 PM