| |
|
| |
Expeditor user interface team best practices on toolbar and menu contributions |
| |
|
| |
OverviewComponent properties allow developers to create code that at compile time has specific function but accepts flexible input at runtime. For example, a developer can create a component that uses a predefined component property to update the title tab's text within a composite ... |
| |
|
| |
Overview
When multiple users share the same workstation, the configuration is referred to as a multiuser installation. This means that a single Expeditor client exists and is shared among all users; however, each user has their own workspace containing configuration details specific to that ... |
| |
|
| |
Overview
By default, Eclipse plugins are lazy. Lazy is the technical term (located in the bundle's manifest) that means that plugins are started when a request is either directly made by the Platform to start the plugin or indirectly through class loading. For example, the latter case implies ... |
| |
|
| |
Overview
The enhanced HTTP client in Expeditor allows developers to quickly create code that requests data from remote servers over HTTP or HTTPS. The enhanced client wraps the standard Java URLConnectionclasses such that authenticated requests leverage the Accounts framework and HTTPS ... |
| |
|
| |
Overview
It's often the case that developers must write secure code that interacts with secure resources such as sockets or web services. After creating code to communicate over the HTTPS protocol, developers are normally confronted with SSL errors. For example, the following error is typical. ... |
| |
|
| |
Overview
The Lotus Expeditor micro broker component is a small message broker that provides a messaging fabric for integrating various parts of a solution such as applications and small devices located at the edge of the network. A message broker ensures that messages arrive at the correct ... |
| |
|
| |
Overview
Lotus Expeditor Client for Desktop uses Eclipse Activities (org.eclipse.ui.activities) to dynamically add an remove items from the user interface. Actions such as menu items or tool bar can be grouped together under a single activity ID. When the activity does not apply to the current ... |
| |
|
| |
Overview
Various features add contributions to the launcher (Open) menu. These additions may be added declaratively via the launcher extension point or programmatically. A common request is to remove specific items to suit customization. How might one remove such items? LauncherManager
The ... |
| |
|
| |
Overview
The Expeditor desktop client may prompt the user to login to the platform. This is sometimes referred to as platform SSO on the wiki. It may be required that custom application code only execute after the login process is complete. In such a scenario, how can code know when the login ... |
| |
|
| |
The global install handler supports the creation of desktoprelated objects. This article demonstrates how shortcuts created by the install handler can be removed. |
| |
|
| |
This sample supplements the "Using Dynamic Variable Substitution in Composite Applications" found on the IBM Composite Applications Wiki. |
| |
|
| |
This sample demonstrates the usage of Java™ Server Pages (JSPs) within a Web application intended for deployment on the local Web Container. The sample demonstrates deployment on a Windows Mobile device. |
| |
|
| |
The accounts framework provides a programmatic means of creating, accessing, and interacting with account data. |
| |
|
| |
Local portlets can be accessed by Expeditor clients. This sample demonstrates a functional portlet and adds an icon to the portlet's title bar. |
| |
|
| |
The accounts framework provides name, password credentials to various backend servers. If required, Axis web services can be used in conjunction with the accounts framework to provide WS security data to the application server. |
| |
|
| |
Synchronization involves updating the desktop client with information such as managed settings and composite applications. The desktop client offers an API to control synchronization as well as out of the box features. |
| |
|
| |
While Lotus Expeditor does not directly provide support for JAXWS, the Java 1.6 runtime provides the necessary support to use JAXWS clients on the Lotus Expeditor platform. |
| |
|
| |
This demo illustrates how to run the Order Entry sample using the toolkit. |