JAX-RS (JSR 311) is the community-driven Standard for building RESTful web services with Java. The reference implementation for JAX-RS is Jersey and ships as OSGi bundles. Unfortunately the OSGi integration does not provide much more. To properly use Jersey in an OSGi context, a number of bootstrapping issues must be overcome, including:
Standard [35 minutes]
BIRT is a powerful framework for adding data visualization and reporting capability to your application. However, creating BIRT designs is only part of the story. To create a seamless application experience, you must integrate BIRT into your application.
This presentation will walk you through the BIRT architecture and demonstrate several different ways to integrate BIRT into your application from running reports with the APIs to integrating BIRT into Web Applications.
OSGi is a set of open standards describing a dynamic module system for the Java language maintained by the OSGi Alliance.
Concierge strives to be a minimal footprint implementation of the OSGi core standards particularly targeted for resource-constrained embedded devices.
While the existing version has targeted OSGi R3, there are ongoing efforts to bring Concierge under the Eclipse umbrella and make it compliant with the current OSGi R5 standard.
Vert.x is a lightweight, high performance, application platform for the JVM that's designed for modern mobile, web, and enterprise applications.
In this talk you will be presented with an overview of Vert.x - what it is, and what it can be used for, and with the help of a few demonstrations, we'll take you on a tour of it's main features, including the clustered event bus, the module system and high availability.
Some years ago eclipse foundation introduced their amazing ideas concerning e4. The UI should not be related to SWT anymore, but different ui technologies should be available. Eclipse implemented a UI renderer for SWT.
Rushan Gillmulin started a project called Vaaclipse. It is based on the e4 runtime and adds a Vaadin UI renderer. So an RCP application based on e4 and Vaadin UI can be implemented properly.
In my talk i am going to demo how easy it is, to implement an RCP application using Vaaclipse.
Choosing a modeling technology, is too often reduced to the selection of either UML or DSL. Even so, in practice, we often need both: UML and profiles to benefit from a standard and off-the-shelf mature tools, and DSL to benefit from a custom notation over a custom data structure.
Rather than opposing these approaches, Sirius can be used to efficiently combine existing UML modelers with DSL-based tools.
At its core, the iAware team develops a reusable application platform built on top of the Eclipse RCP framework to provide the ability to create targeted healthcare workflow applications. As such when making the decision to upgrade from Eclipse 3.X to Eclipse 4.X we had to balance the cost and risk with the expected gains that the new feature set will bring; especially in our case where the end-user doesn't see the changes but would definitely feel them if things don't work right.
At EclipseCon last year  I gave a talk on the plans to do a major redesign of the Equinox core framework for the Luna release. Now that we are in the middle of the Luna development cycle I will give an update on the overall progress of this effort and some of the challenges faced while doing such a major change to a core piece of the Eclipse platform. A majority of the development effort for Luna is focused on refactoring and, in many cases, rewriting the core Equinox Framework implementation to be based on the OSGi generic dependency model.
EGit 3.0 shipped with Kepler and is shipping new releases every 3 months. Curious what's in ?
Did you know that EGit supports interactive rebase with a graphical UI and that you can interactively stage/unstage individual hunks ? When using git blame annotations in order to understand which commit has last touched a certain line in a source code file you can now quickly iterate through the history of this line.