Learn all about the second version of the Java Portlet Specification (JSR ). In Version , the specification and the APIs more than doubled. The Java Portlet Specification addresses the requirements of aggregation, was approved by the Java Community Process in March as JSR This tutorial on JSR development provides an introduction to portlet programming as the reader is taken through the creation of a simple HelloWorld portlet.
|Published (Last):||21 March 2006|
|PDF File Size:||8.12 Mb|
|ePub File Size:||13.23 Mb|
|Price:||Free* [*Free Regsitration Required]|
Inter portlet communication is mechanism to send or receive data between two portlets. In both cases, the portal needs to know what kind of events a portlet can receive and send.
Therefore, the JSR specification lets you indicate for which portlet modes the portal should display UI controls as part of the render response using the method setNextPossiblePortletModes. Share to Twitter Share to Facebook.
What’s new in the Java Portlet Specification V2.0 (JSR 286)?
This method portoet a hint to the portal about how much information the target serveResource call requires. In the first version of the Java Portlet Specification, the portlet could not contribute to sections of the portal page outside its portlet window.
This practice is common for Ajax applications, which can particularly benefit from the 2866 enhancements that version 2. A portlet can aggregate integrate and personalize content from different sources within a web page.
This implementation means that changing a render parameter, for example, requires an update of all the URLs on the page, which the portal cannot perform, as the processing of the response data on the client is done entirely by the portlet.
View image at full size. Here Portlets catalog are of use.
A QName consists of a namespace for example, http: Access to all these life-cycle porylet gives you many hook points for managing objects related to these lifecycles, which is a great feature for many frameworks. Because the markup returned from serveResource is not aggregated with other markup from the portal framework, the resource response allows full control over the output stream.
This is one of the good features. The expert group of JSR consists of all the major commercial and open-source portal developers, portlet bridge developers, and portlet framework developers.
Newer Post Older Post Home. If you have portlets that are not customizable and don’t display different content for different users, such portleg a news-of-the-day portlet, then you get a cache entry for each user, even if all entries are the same.
This will add advantage to perform some events or some actions before portlet is rendered. Ideally, set the expiration time to a high value so that the markup is cached for a long time.
Standard portlet API
Another State in Portlet Lifecycle. This capability opens the possibility to create new functionality by combining existing components into portelt mashups in a similar speification to popular Web 2.
The define objects tag is now enhanced and gives you the following additional variables beyond the request, response, portletConfig from the V1. Now the user interacts with Portlet 1 and triggers an action on Portlet 1. Public render parameters are another way in IPC.
Java Portlet Specification – Wikipedia
You can specify a full QName for each event, or if you use the same namespace for many events, you can declare it as the default namespace and then specify only the local part of each event. Support for WSRP 2. JSR is the Java Portlet specification v3. Portlets 2 and 3 define that they are able to receive event A in their portlet. Types of portlet solution vertical domains wpecification technology like collaboration, social networking, community, content management, utility, calendaring, HRM all are available in these catalogs.
You can find a complete list of the members of the expert group here. The following are important Specification and Features.
What’s new in the Java Portlet Specification V (JSR )?
A portlet may want to send an event to a remote portlet that is running using WSRP. In the resource request, the parameter handling lets you have access to three different types of parameters:. GenericPortlet also lets you use the following annotations to make dispatching life-cycle calls to specific handler code easier:. In most cases, the portlet code does not actually need to change whether a render parameter is public or private, so you can enable your portlet for coordination by simply declaring those parts of the view state information in the portlet.
Typically, connections are defined explicitly at page creation time, or they are automatically inferred by the portal at runtime.