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.

Author: Gutilar Kagar
Country: Czech Republic
Language: English (Spanish)
Genre: Health and Food
Published (Last): 22 April 2004
Pages: 124
PDF File Size: 15.34 Mb
ePub File Size: 17.43 Mb
ISBN: 475-2-80772-269-8
Downloads: 43781
Price: Free* [*Free Regsitration Required]
Uploader: Nektilar

When constructing XMLAccess scripts for use in installing standard portlets, use the following values: Use this file if you use services from the Public SPI javadoc package. View the basic steps for creating a simple portlet, that include writing the portlet code, compiling java source, creating the JAR file, writing the portlet tutorkal, setting up the WAR file directory structure, and packaging and deploying portlets. There are number of differences between the elements in this example and the corresponding Figure 8.

The Hello World portlet provides an introduction to writing your first portlet. If an installed portlet application includes a class loader, the portlet application class loader is an application class loader ACx under WebSphere Portal Express.

Use this file if you use services from the Public API javadoc package. If you are familiar with the web. The application server searches for security policy files in the location tytorial the enterprise application archive rather than the Web application archive.

If you suspect a classloading problem, ensure that the required classes jssr in the appropriate classpath according to the classloading hierarchy.

Before you package your portlet, the class files and resources must be arranged in the WAR file directory structure described here. The WAR file format contains the Java classes and resources that make up one or more portlets in a portlet application. Before you begin developing portlets, set up an environment that makes the tasks of writing, compiling, and testing portlets easier. Rational Application Developer provides wizards to help you build, test, and deploy portlets using all of the APIs and related classes and interfaces available in the portlet run time environment.


This is especially useful for portlets that use messaging because these portlets have to be placed on the same page.

Creating a simple portlet

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.

Then, compile the portlet using the fully qualified path to the Java portlet source. Next, the portlet must be packaged in the JAR file format. The resources can be images, JSP files, Writing the portlet descriptorsand property files containing translated message text. Runtime classpath RP branches from runtime classpath patches. That is, the WAR file name can be changed, but the uid must indicate the original uid used during portlet installation.

For more information, see The XML configuration interface. The following shows the minimum elements required for the standard portlet deployment descriptor. Therefore, the portal server copies was. 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. See Sample portlets for more information.

Creating a simple portlet

Application class loaders AC1application class loaders AC2and application class loaders AC3 are portlet applications that branch from application extensions. GenericPortlet which also can throw a PortletException. If this value has not been specified, specify the WAR file name of the portlet application in its place. On a portal server running on Windows, installing a WAR file with a name that is jr than 25 characters will result in an error.

If you are not using wizards to develop portlets, the following topics describe the mechanics of building a simple portlet.


Packaging portlet classes, resources, and descriptive information in nsr single file makes distribution and deployment of portlets easier. Runtime extensions RE branches from runtime classpath, and application extensions AEX branch from runtime extensions.

To do this, proceed as follows: Hello World provides the fewest methods required for a portlet. For example, a portlet application might use a portlet descriptor as follows: The XML configuration interface allows the portlet developer to specify places, pages, themes, skins, supported markups and clients, and other settings for a portlet application. You can also run the build-war-file or build-ear-file tasks to build the.

Because Windows limits the maximum path length to characters, the name of the WAR file must be less than 25 characters. Portlets contained in WAR files have the advantage of being dynamically downloaded and installed.

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. 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.

After installation, the portlet is ready for use and does not require the server to be restarted. Omit this tag if the portlet does not use this feature. You can also build portlets using your own jr environment and tools.

Refer to the documentation for Rational Application Developer for complete setup instructions. For portlet updates, the WAR file name must be the original name of the WAR file used to install the portlet application.

It uses the portlet response object to write simple output directly to the portal page.