These tutorials, CBTs and tips are designed to help any Java professional who is looking to acquire JSR development skills to become quickly adept at both. In this three-part series, the articles describe new features available in the Java Portlet Specification (JSR ) and extensions supported by OpenPortal. Portlet Tutorial, Java Portlet, Portlet Example, Java Portlet Tutorial, What is Portlet , JSR has introduced the using of annotations for controlling things were.
|Published (Last):||2 May 2010|
|PDF File Size:||8.2 Mb|
|ePub File Size:||6.11 Mb|
|Price:||Free* [*Free Regsitration Required]|
Packaging portlet classes, resources, and descriptive information in a single file makes distribution and deployment of portlets easier. In the following graphic runtime classpath patches RCP is located at the top of the hierarchy. The application server searches for security policy files in the location of the enterprise application archive rather than the Web application archive.
The WAR file format contains the Java classes and resources that make up one or more portlets in a portlet application. WebSphere Portal Express includes an administrative portlet for installing, uninstalling, and updating portlets. For example, a portlet application might use a portlet descriptor as follows: If you suspect a classloading problem, ensure that the required classes are in the appropriate classpath according to the classloading hierarchy.
A particular class loader can reference other classes as long as the other classes can be loaded by the same class loader or any of its ancestors, but not its children.
For portlet updates, the WAR file name must be the original name of the WAR file used to install the portlet application. The portlet is provided along with the source in the IBM Portlet Samples package, which is available from the portlet catalog by searching for navcode 1WPZ. The Hello World portlet provides an introduction to writing your first portlet. Runtime extensions RE branches from runtime classpath, and application extensions AEX branch from runtime extensions.
Portlets contained in WAR files have the advantage of being dynamically downloaded and installed. Application class loaders AC1application class loaders AC2and application class loaders AC3 are portlet applications that branch from application extensions. You can also build portlets using your own development environment and tools.
A portlet application exists as a structured hierarchy of directories. Standard portlets Table 2. After installation, the portlet is ready for use and does not tutofial the server to be restarted. Compile your Java source files. Before you package your portlet, the class files and resources must be arranged in the WAR file directory structure described here.
To do this, proceed as follows: Tuorial uses the portlet response object to write simple tutorrial directly to the portal page. If you are not using wizards to develop portlets, the following topics describe the mechanics of building a simple portlet.
This is especially useful for portlets that use messaging jssr these portlets have to be placed on the same page. The resources can be images, JSP files, Writing the portlet descriptorsand property files containing translated message text.
You can also run the build-war-file or build-ear-file tasks to build the. Omit this tag if the portlet does not use this feature. When constructing XMLAccess scripts for use in installing standard portlets, use the following values: Runtime classpath RP branches from runtime classpath patches.
Creating a simple portlet
For more information, see The XML configuration interface. Because Windows limits the maximum path length to characters, the name of the WAR file must be less than 25 characters. Use this file if you use services from the Public SPI javadoc package. Therefore, the portal server copies was. There are number of differences between the elements in this example and the corresponding Figure 8.
That is, the WAR file name can be changed, but the uid must indicate the original uid used during portlet installation.
The portlet information directory is not part of the public document tree of the application. Then, compile the portlet using the fully qualified path to the Java portlet source. Hello World provides the fewest methods required for a portlet.
If this value has not been specified, specify the WAR file name of the portlet application in its place. To deploy a portlet and run it on the server, it must be packaged in the form of a Web application ARchive or WAR file. The following shows the minimum elements required for the standard portlet deployment descriptor.
On a portal server running on Windows, installing a WAR file with a name that is more than 25 characters will result tuttorial an error.
GenericPortlet which also can throw a PortletException. Tutoria, XML configuration interface allows the portlet developer to specify places, pages, themes, skins, supported markups and clients, and other settings for a portlet application. To facilitate deployment of portlet applications and complex portlets, you can provide a portlet configuration file that can be invoked by the XML configuration interface XMLAccess.
Use this file if you use services from the Public API javadoc package. You can set up the run time environment for debugging portlets on the local development machine or on a remote server. Refer to the documentation for Rational Application Developer for complete setup instructions.
Creating a simple portlet
Next, the portlet must be packaged in the JAR file format. Before you begin developing portlets, set up an environment that makes the tasks of writing, compiling, and testing portlets easier.
The graphic illustrates where WebSphere Portal Express and portlet applications fit into the classloading hierarchy.