Overview > Eclipse RCP Integration

Eclipse RCP Integration

Belongs to following categories: ULC5.2, Integration,

Purpose

The Rich Client Platform (RCP) introduced in Eclipse 3.0 enables Eclipse to be used as a platform for arbitrary rich clients. The plug-in architecture of Eclipse qualifies Eclipse in a natural way to act as a portal to any business applictions.

This contribution shows how ULC applications can be integrated into such a Eclispe RCP portal. As an example this contribution integrates the Online Shop sample application from the ULC website.

Resources

Download the complete source code here.

How to use

Deploy the Online Shop View Plug-in into the desired Eclipse installation.
Start Eclipse.
Select the Windows -> Views menu item.
Select the ULC -> Online Shop View Plug-in tree node. This will open an view that displays the Online Shop sample application from the ULC website inside Eclipse.

How it is implemented

The Online Shop View Plug-in adds a customized applet launcher as only widget to the view. This customized applet launcher defines the application URL to connect to. Moreover a custom look and feel is installed.

Please note that the plug-in description defines all libraries to be included in the class path of the plug-in (i.e. all ULC client libraries and the look and feel library).

Compatibility

The described functionality has been developed and tested using JDK 1.4.2_01 and ULC 5.2.

one comment (by Swaraj) | post comment

labels

Category:	ULC5.2
Category:	Integration

attachments

Created by daniel. Last edited by admin, 6 years and 201 days ago. Viewed 13,465 times. #2

[diff] [history] [edit] [rdf]

Swaraj, one year and 29 days ago.

Thanks for the reply. I guess it depends on your tiiinedfon of practical. It's mostly a one-time issue (you could re-use a Target template once you had created one), but just about every plug-in has a collection of a dozen or so localized fragments, so the opportunity to goof and miss a couple certainly exists. And it can be even messier if you add plug-ins to the target and/or want to add languages to the target later. A runnable target (and I appreciate why it isn't, out of the box) would alleviate much of that through use of the Eclipse update mechanism.I've done this by hand to add Spanish to the product and I focused on plug-ins that were likely to have UI visible components (and it seems fine), but I didn't copy the NL fragments for every plugin in the target (and I realize I probably should) and because it is a very manual process, my temptation is to copy in all of the NL fragments whether I need them or not just so I won't have to go through it again but that seems wasteful. I'm still a bit of a noob and was just hoping there was a better answer.