Version of the Portlet Specification plans to align with J2EE , integrate other new JSRs relevant for the portlet, and align with the WSRP specification V Learn all about the second version of the Java Portlet Specification (JSR ). In Version , the specification and the APIs more than doubled. Version of the Java Portlet Specification extended the capabilities to was approved by the Java Community Process in March as JSR
|Published (Last):||17 May 2015|
|PDF File Size:||16.43 Mb|
|ePub File Size:||19.15 Mb|
|Price:||Free* [*Free Regsitration Required]|
In msr, these cacheability levels give you the ability to provide as many hints about the cacheability as possible to the runtime. This setting means that the portal can generate a URL that does not contain any interaction state of the page and the portlets on the page. The Java Portlet Specification V1. In both cases, the portal needs to know what kind of events a portlet can receive and send. Some of its major features include: Portlet Filter and Listeners.
JSR Portlet Specification Final Release
Because the portal does not know specific semantics of the portlet-managed modes, it does not know when it makes sense to present a decoration to switch to a portlet-managed mode and when it does not. You must have a resource URL to trigger the new serveResource life-cycle method. In the second version, you can set cookies, document head section elements for example, HTML ones such as meta, link, or style and HTTP headers such as application-specific Pragma headers.
In addition to these options, specific portlet container implementations may provide their own options. We will define some public render parameter such a way it will available to other portlet to get the data from that. Instead, you needed an additional servlet that served the resources. First, you provide the general event definition, and then you reference this definition in the portlet section with tags that specify that the portlet can either receive or send this event.
The JSR tag library has its own namespace so that new additions do not interfere with portlets using the old JSR tag library. The new Portlet Specifications will add functionality that was not addressed in the first version specification, other JSRs were not final at the time JSR went to public review e.
Typically, connections are defined explicitly at page creation time, or they are automatically inferred by the portal at runtime. A portlet may want to send an event to a remote portlet that is running using WSRP. This will add advantage to perform some events or some actions before portlet is rendered. A portlet container is not responsible for aggregating the content produced by the portlets; the portal itself handles aggregation.
The Java Community Process(SM) Program – JSRs: Java Specification Requests – detail JSR#
One advantage of serving resources through a servlet is less overhead because the request does not have to pass through the additional portal framework, for example, when serving large media streams. Here another method added in lifecycle so that it send or publish the events and when page render respective listener portlets receive the dada or events.
GenericPortlet also lets you use the following annotations to make dispatching life-cycle calls to specific handler code easier:. Thus, the browser can cache the returned markup of the serveResource call for at least as long as the user interacts with the current page. Because the markup returned from pprtlet is not aggregated with other markup from the portal framework, the resource response allows full control over the output stream.
After doing its preprocessing, the filter implementation can either terminate the request processing or call the next element in the filter chain, passing in either the received request and response or additional wrappers.
Standard portlet API
One example involves implementing a mapping of resources to shared IDs. This article provides an overview of the main new features in JSR and some examples of how to leverage specifiction features. This markup is intended to be aggregated with other markup fragments into a larger application, for example, a portal page as shown in figure 1.
You should not modify state that affects other portlets because the portal framework does not have a chance to update other parts of the portal page for serveResource calls, so that updates to page-level state may not be visible. Validation-based caching is useful for situations in which you portlef not want to recompute the markup of a portlet often because it is an expensive operation.
If you want to provide the portlet with additional capabilities, set an object providing access to these capabilities as a request attribute. Why do we need this additional JAXB serialization? Note that ResourceURLs cannot set new render parameters, jssr mode, or window state. Each filter gets the current request and response, or a wrapped version created by a preceding filter, and the filter chain.