Each filter interface extends a common base interface named javax. This common base interface contains two methods: init javax. FilterConfig filterConfig and destroy. The init method ensures that every filter has access to a FilterConfig object from which it can obtain its initialization parameters: a reference to the PortletContext that it can use, for example, to load resources needed for filtering tasks. The destroy method signifies the end of service of the filter. The init and destroy methods of a portlet filter are called only once during their lifetime.
|Published (Last):||8 December 2013|
|PDF File Size:||8.17 Mb|
|ePub File Size:||2.83 Mb|
|Price:||Free* [*Free Regsitration Required]|
Section 2: Request 2. Please provide details here for which platform editions are being targeted by this JSR, and how this JSR has considered the relationship with the other platform editions. 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.
J2EE 1. These areas were not addressed in the first version of the Portlet Specification. Version 2. To be determined by the expert group, initial target is to have a working EG by December , a early public draft beginning of , a public draft by mid and a final version by end of We anticipate a mixture of mailing list and occasional face to face or teleconference meetings.
The Executive Committees would like to ensure Spec Leads understand the value of this transparency and ask that each JSR have an operating plan in place for how their JSR will address the involvement of the community and the public.
Please provide your plan here, and refer to the Spec Lead Guide for a more detailed description and a set of example questions you may wish to answer in your plan. We will provide early public drafts in order to get public feedback as early as possible.
Include version information for the profile or platform in your answer. The RI will be implemented inside the open source project Pluto at Apache. Not applicable 2. If this specification, or a future version of this specification, is included in a future version of a Java platform specification, this specification will remain available for use outside the platform specification, and will continue to be evolved outside the platform specification.
Section 3: Contributions 3. Please include links to the documents if they are publicly available. Portlet Specification, Version 1.
Java Portlet Specification
Overview Portlets are web-based components that enable integration between applications and portals and thus enable delivery of applications on portals. The Java Portlet Specification achieves interoperability among portlets and portals by defining the APIs for portlets. The Java Portlet Specification 1. This brought a world of difference. By adhering to the standards, you can build portlets that can run in portals, irrespective of their vendors. Since its release in , JSR has gone through many real-life tests in portal development and deployment.
Section 2: Request 2. Please provide details here for which platform editions are being targeted by this JSR, and how this JSR has considered the relationship with the other platform editions. 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. J2EE 1. These areas were not addressed in the first version of the Portlet Specification.