seen

With the Indigo release the BIRT project now has a new runtime. This runtime is POJO based and offers easier deployment than previous versions of BIRT. This presentation will take you through the various ways the new POJO BIRT Engine and BIRT Viewer can be deployed and extended. This will include topics such as deploying the BIRT Engine with Spring, integration with JBoss SEAM, the BIRT Viewer architecture and creating your own servlet using the BIRT Engine.

Topics covered include:
BIRT Overview and Architecture:
BIRT Deployment:
BIRT Viewer Architecture

Internationalization denotes a pervasive programming approach for building multilingual applications efficiently. However, dramatically often, the expected advantages get lost. Reasons therefore are a missing overview of the concepts provided in the Java programming language as well as their error prone integration in the development process.

TapiJI (Tooling for agile and process integrated Java Internationalization) helps solving these problems. Its architectural design is separated into a “Tool suite” and a “Translator” component. The “Tool suite” integrates into the Eclipse IDE of Java developers and interactively assists them in performing Internationalization as an integral part of day to day development work. At the same time it abstracts from low level issues that arise while working with the built in Java Internationalization tooling. The same abstraction is provided as an API to enable the development of third party extensions to support further Java Internationalization frameworks. On the other hand, the “Translator” component is designed for assisting in the translation process. It is realized as a rich client application by using the concepts provided by the Eclipse Rich Client Platform (RCP) and tuned to support translation specialists without a profound technical knowledge.

EMF Ecore models are often used to generate code for data models in Eclipse applications. Even E4 uses EMF to describe its data, the workbench model. EMF Ecore models are stored in Ecore files and are version-controlled by a source code repository such as SVN, CVS or Git. However these repositories do not offer specific support for merging Ecore files and therefore merging is difficult and error-prone.
EMFStore offers support for conflict detection and merging including Ecore, but it requires the installation of a server instance in addition to the existing source code repository.

We, the Jubula project team members, recently open sourced main parts of the commercial UI testing tool GUIdancer and participated with our newly created Eclipse project in the Eclipse Indigo release train.

Joining the train required a lot of effort to meet the versatile internal and external artifact requirements. We start by looking at the specific needs we had:

• Open your source: a pre-requisite for an external build process to take place is the external presence of the sources to build in combination with the absence of non-EPL conform code and artifacts (JARs).

RAP is known as a Web framework for Eclipse applications, able to bring complex RCP UIs into the browser. But its leightweight and powerful Java-only widget toolkit layer is now also available for other types of OSGi-based applications.

In the latest version, RAP provides an OSGi service that allows to configure and start RAP applications programmatically. With this new service, RAP is able to run on any standard OSGi implementation. It is also possible to start different RAP instances in parallel and bind them to selected HTTP services.