To enable interoperability between Portlets and Portals, this specification will define a set of APIs for Updates to the Original Java Specification Request ( JSR). The Java platform provides an standard referred to as JSR that standarizes how portlets interact with portlet containers and ensures compatibility across. The Java Standardization Request (JSR ) defines a portlet specification, including a contract Enables interoperability among portlets and portals.
|Published (Last):||14 December 2006|
|PDF File Size:||8.90 Mb|
|ePub File Size:||2.79 Mb|
|Price:||Free* [*Free Regsitration Required]|
We could have alternatively implemented the javax. However, it does not address aggregation, security and personalization. Here Portlets catalog are of use. By abstracting the repository-specific code, we are able to keep the display and portlet classes unchanged, regardless of the source of the documents. A Portlets Catalog is a set of portlets that are ready-to-use components for enterprise portals.
The Portlet Specification defines an expiration based caching mechanism. This simple class acts as the broker for the actual content-source implementations. In this article, we examine a portlet that Wingspan Technology where we work developed and contributed to the open-source community.
There will be no shared code requirements. For those who want to adopt portals certainly need many and variety of portlets to deploy and run. This is important because this is how our view.
Configuring JSR 168 portlets
With the introduction of the JSR specification, open-source portals are starting to take large bites out of the portal market. In some portals, like eXo, the portlets are even responsible for the portal navigation.
Language specific portlet information Property Name Description Resource Bundle To provide language specific portlet information, like title and keywords, resource bundles are used. This way, there might portleets SharePointSourceJdbcSourceand the like, and the administrator can change the source without any recompiling.
JSR IBM extension for cooperative portlets
Portlet class Property Name Description Portlet class The canonical name of the portlet selected in the Portlets list box. Any portals using the older versions of Tomcat, including Pluto the reference implementationhave problems using the application session across web contexts. Name Name of the preference. Another enhancement would be to provide a caching mechanism at the portal level.
It used to be that if you wanted to migrate portlet functionality from one portal to another, you would have to rewrite massive amounts of code. Used in the xml: With the increased adoption of Java portals, both as intranets and public sites, comes the need to separate portlet functionality from the portal to both maximize code reuse and limit your dependency on specific vendors.
Jrs components will comprise -but they will not be restricted to-: If SharePoint were the source, these properties might be the site name and document library name, respectively. It also provides persistent storage mechanisms for the portlet preferences.
Additional settings must also be provided using a deployment descriptor extension ibm-portlet-portal-ext. An administrative name used to identify the portlet. Portlets are pluggable user interface software components that are managed and displayed in a web portalfor example an enterprise portal or a web CMS.
Provide Administrators with a mechanism to specify the folder to display and connection information for Documentum. Remote cache scope shared indicates that the remote cache is shared. Now, as portal vendors begin to support the Java Specification Request http: This specification will establish a standard API for creating Portlets, thus ksr locking in Portal developers in a specific implementation and allowing Portlets developers to reach a wider audience while reducing pirtlets development efforts.
Java Portlet Specification – Wikipedia
The Java Portlet Specification defines a contract between the portlet container and portlets portletts provides a convenient programming model for Java portlet developers. A portal is a web application whose primary purpose is to aggregate web content in portlets.
The portlet class loads the Java Server Page JSP file that is, in turn, responsible for calling the content classes and displaying the folder contents. Many of them require the WAR to be run through a preparation tool or some other multistep deployment process.