| < Day Day Up > |
|
We prepared the samples in this chapter using WebSphere Studio Application Developer version 5, and Portal Toolkit version 4.2.5. Both were introduced in earlier chapters. In addition, we used Domino Toolkit for Java version 2.1, which is described in the following section.
The Lotus Domino Toolkit for Java/CORBA, commonly referred to as "the Java/CORBA toolkit," is a comprehensive source of samples, documentation, and software that helps you in your Java development work.
The overall goal of the Java/CORBA toolkit is to help you leverage the power of Java, Domino, CORBA, Notes, and Portlets. This toolkit is suitable if you are developing:
Java programs, such as portlets, that use Domino Objects for Java to access local and remote Domino data and services
Java programs that access data in relational database management systems
Java and C++ programs that use the Common Object Request Broker Architecture (CORBA), the Internet Inter-Operability Protocol (IIOP), and the Domino Interface Definition Language (IDL) to access remote Domino objects
It provides a range of sample code you can use to create your own Java programs. However, it does not provide sample code based on portlets because this toolkit was released before WebSphere Portal server existed. Nevertheless, it is very helpful for portlet development work.
Important: | Domino Toolkit for Java includes the Domino Objects for Java libraries (Notes.jar and NCSO.jar) that let you develop local and remote Java programs. NCSO.jar lets you develop remote Portlets without necessarily having Domino or Notes installed. |
You can download this toolkit from:
http://www-10.lotus.com/ldd/toolkits
The hybrid integration techniques will start where the JSP option left off, and introduce some additional functionality with Java components. The functionality we add will focus on the Customer List portlet, where we incorporate the following features:
Search for customers
Paging capabilities
We will end up with a portlet that can manage long views since it offers positioning and filtering capabilities, while retaining the previous enhancements like Click to Action and People awareness.
Figure 6-1 shows the different portlet modes in the Portal UI and how the portlets operate. The figure also includes the .java package and actions inside that Java file.
Figure 6-1: Hybrid JSP- Java Customer List portlet
| < Day Day Up > |
|