构建Lotus Expeditor V6.1的Eclipse插件应用

4星 · 超过85%的资源需积分: 10 119 浏览量更新于2024-07-29 收藏 2.69MB PDF 举报

“Eclipse插件开发 - Lotus Expeditor组件应用详解” 在 Lotus Expeditor 组合应用程序中，Eclipse 插件开发是一个重要的主题。本文档深入介绍了可以在这些应用程序中使用的不同类型的组件，并且展望了未来的发展趋势。文档涵盖了以下核心组件类型： 1. **本地Eclipse组件**：这部分主要概述了Eclipse插件的概念。Eclipse插件是构建在Eclipse Rich Client Platform (RCP) 上的自包含模块，它们扩展了Eclipse IDE的功能。开发者可以通过实现特定的接口和使用Plug-in Development Environment (PDE) 工具来创建和管理这些插件，使Eclipse能够处理特定的任务或集成外部系统。 2. **Portlets**：Portlets是在Web应用程序中用于提供交互式用户体验的小型应用程序单元，通常在portlet容器中运行。在Lotus Expeditor中，将portlet应用迁移到客户端容器时，需要考虑如何保持其在不同环境下的兼容性和功能完整性。开发者需要了解portlet生命周期、渲染机制以及与Eclipse插件之间的通信方式。 3. **Web应用程序**：文档详细阐述了客户端的Web容器，这是在桌面环境中运行Web应用程序的关键。开发者可以利用这个容器来展示基于HTTP的Web内容，同时利用Eclipse平台提供的特性，如工作台集成、菜单和工具栏支持等。 4. **未来组件类型**：文档还讨论了可能作为未来组件的候选技术，这可能包括更深入的SOA集成、移动应用程序支持或其他新型应用框架。随着技术的不断发展，这些新组件类型将为开发者提供更多工具和可能性，以适应不断变化的软件需求。《构建Lotus Expeditor V6.1中的组合应用程序》这篇红皮书由Juan R. Rodriguez、Alex Barbosa Coqueiro、Rafael Sanchez和Robert Schneider共同撰写，旨在帮助读者理解如何在面向服务架构（SOA）环境中组装管理型客户端应用。书中详细解释了RCP组件和portlet组件之间的通信，以及如何部署复合应用程序。此文档适用于Lotus Expeditor V6.1的Version 6, Release 1。尽管基于预发布版本，但书中提供的信息对于理解Eclipse插件开发和Lotus Expeditor的应用有很高的价值。不过，对于产品的最新更新和功能，建议查阅产品文档或后续版本的红皮书以获取最准确的信息。

2 Building Composite Aplications in Lotus Expeditor V6.1

1.1 Overview

Whenever you are facing an application that is homogeneous, which is a sole

application composed of several other different heterogeneous applications but

behaves like a unique application, you are probably facing a composite

application.

In order to behave like a unique application, a composite application needs to

offer inter-component interaction capabilities. This means that components of a

composite application are required to be able to work and interact with other

components. For the remainder of this paper, we will refer to these kind of

components as cooperative components.

Cooperative components which make up a composite application should remain

loosely-coupled. This would prevent, for example, the composite application to

fail or behave incorrectly if one or more components are dynamically added or

removed from it. We will unveil more composite applications features in the rest

of this chapter, but first we are going to analyze the difference between server

based and managed client composite applications.

1.2 Server based and managed composite applications

Nowadays we are quite used to Web applications made up of different fragments

which are aggregated at the server side, such as portal applications. But this

pattern is giving way to a new means of executing composite applications at the

client side, therefore enabling the client to run a composite application in a

non-connected environment.

Important: Server based and managed client composite applications are both

defined, described or composed at the server side. However, server based

composite applications are instantiated at the server side, whereas managed

client composite applications are instantiated at the client side.

Chapter 1. Composite applications 3

Server based composite application pattern

Figure 1-1 illustrates a server based composite application pattern. When the

client requests a page to the Web or portal server, it is actually asking it to

generate a formatted page with information from different sources.

Figure 1-1 Server based composite application pattern

Internally, the Web or portal server analyzes the application model to find out

what components make up the composite application, applies role-based access

based on the user’s identity, retrieves the corresponding information to be

presented, looks up the layout, and finally aggregates all the content in a

formatted page. Finally, it will send the resulting page to the client, which will

display it with its Web browser.

A typical example of a server-based composite application infrastructure is a

portal server serving formatted Web pages after Web browsers’ requests at the

clients. In that case, a requested page contains one or more portlets, which is

accessible according to a certain policy, and is able to cooperate between them

by means of a wiring mechanism.

Managed client composite application pattern

In the case of a managed client composite application, the instantiation of the

composite application is not made at the server side but at the client side. In

other words, an XML document of the application model is deployed to the client.

This XML document describes the instructions to create the aggregation on the

client of the different components composing the application. The client then

looks all these components up locally and aggregates them into a graphical

representation. These components usually access local information which could

be received from a remote server or even another application. If it happens that a

required component is not found locally, it will be retrieved remotely. This is

possible because the XML document contains enough information to indicate

where the required component could be downloaded from.

Note: Portal applications are a specific type of application, in particular a

portal application is a collection of pages, portlets, policies and roles.

aggregated page

page request

browser

WebSphere

Portal

Composite

Applications

backend

resources

剩余133页未读，继续阅读

teddy2100

粉丝: 0
资源: 1

构建Lotus Expeditor V6.1的Eclipse插件应用

Eclipse Plugin Development CN

Master Eclipse Plugin Development

Eclipse Plugin Development Session-开源

RDT ruby development tool eclipse plugin

eclipse plugin

Hadoop 0.21.0 Eclipse plugin相关

WDK Eclipse Plugin-开源

Winamp - Eclipse plugin-开源

eclipse plugin源代码 完整工程

最新资源

eclipse plugin源代码完整工程