JavaTM Portlet Specification 2.0：Public Draft for Portlet Development

需积分: 7 40 浏览量更新于2024-07-31 收藏 1.23MB PDF 举报

JavaTM Portlet Specification (PortletSpec_20) 是一项面向portlet开发的行业标准，版本2.0 Proposed Final Draft在2007年11月29日发布，由IBM Corp.担任Specification Lead。这个规范的目的是为了促进Java平台上的portlet技术的发展，这是一种用于Web应用程序中的可重用组件，可以嵌入到企业内容管理系统（CMS）和门户系统中，提供定制化的功能和服务。 PortletSpec_20关注的核心内容包括但不限于： 1. **兼容性与许可**：文档声明为Public Draft状态，意味着它仍处在公开讨论和修改阶段。IBM Corporation允许在任何媒体上无费用或版税地复制和展示这份规范，但必须保留版权通知，链接到官方JCP（Java Community Process）的JSR 286页面（<http://www.jcp.org/en/jsr/detail?id=286>），并确保使用合理的、非歧视性的条款和条件。 2. **版本历史**：此规范基于之前的JavaTMPortletSpecification v1.2.0，发布日期为2003年10月7日，说明PortletSpec_20是在此基础上进行了多次迭代和更新。 3. **专利许可**：IBM承诺永久、非独家、全球范围内的使用其认为必要的专利，这些专利是免费的，且不涉及子许可证转让。这为采用Portlet技术的开发者提供了法律保障，使得他们在遵循规范的同时，不必担心潜在的专利侵权问题。 4. **目标与目的**：PortletSpec_20旨在定义一套通用的标准，以提高portlet的互操作性、可移植性和安全性。它涵盖了portlet的生命周期管理、交互设计、数据模型、事件处理、安全性和部署等方面的要求，以便于开发人员创建可复用的模块，并保证跨多个平台和环境的稳定运行。 5. **社区参与**：鼓励所有对此规范有兴趣的开发者通过邮件jsr-286-comments@jcp.org提交反馈和建议，以推动标准的完善和发展。 PortletSpec_20是Java平台上的一个重要技术指南，它对于任何希望开发、集成或部署portlet的开发者来说，都是一份不可或缺的参考资料。通过遵循这一规范，开发者可以确保他们的工作符合业界的最佳实践，并能够在各种环境中无缝协作。

Java

Portlet Specification, version 12.0 (10/07/20032007)

Gothe(Sun Microsystems, Inc.), Vishal Goenka (SunGard Higher Education), Stefan

Hepper (IBM Corp.), Martin Holzner (Novell, Inc.), Danny Machak (TIBCO Software

Inc.), Kito D. Mann, Benjamin Mestrallet (eXo Platform SARL), Stephen Millidge, Jason

Novotny, Punit Pandey, Ilya Rybak (SAP AG), Charles Severance, Hani Suleiman, David

Sean Taylor (Apache Software Foundation), Julien Viet(JBoss, Inc.), James Ward 5

(Adobe Systems Inc.), Carsten Ziegeler (Day).

We want to give special thanks to (as members of the Expert Group) Subbu Allamaraju,

Wesley Budziwojski, Craig Doremus, Ate Douma, Michael Freedman, Kevin Frender for

their major contributions to this specification.

Finally we would like to thank Torsten Dettborn (University of Jena) who led the TCK 10

and RI efforts

PLT.1.8PLT.1.9 Acknowledgements V 1.0

The Portlet Specification V1.0 is was the result of the work of JSR168 Expert Group,

Subbu Allamaraju (BEA), Chris Braun (Novell), Don Chapman (SAS), Michael

Freedman (Oracle), Laurent Guiraud (SAP), Randal Hanford (Boeing), Andre Kramer 15

(Citrix), Axel Kratel (Borland), Danny Machak (TIBCO), Kris Meukens (EDS), Wes

Mitchell (Broadvision), Takao Mohri (Fujitsu), Dean Moses (Vignette), Andrew Rickard

(ATG), William Seiger (Sybase), David Sean Taylor (Apache), Stefan Hepper (IBM) and

Alejandro Abdelnur (Sun).

We want to give special thanks to (as members of the Expert Group) Subbu Allamaraju, 20

Henning Blohm, Chris Braun, Don Chapman, Adrian Fletcher, Michael Freedman,

Laurent Guiraud, Andre Kramer, Danny Machak, Wes Mitchell, Takao Mohri, Dean

Moses, Peter Petersen, Andrew Rickard and David Sean Taylor for their contributions.

We would like to thank OASIS WSRP Technical Committee, JSR127 Java Server Faces

Expert Group and JSR154 Servlet Specification Expert Group for their cooperation. 25

We would also like to thank all the people who have sent us feedback during the

Community Review and Public Review stages.

Finally we would like to thank Maneesha Jain (Sun) and Stephan Hesmer (IBM) who led

the TCK and RI efforts.

Java

Portlet Specification, version 12.0 (10/07/20032007)

PLT.1PLT.2

Overview

PLT.1.1PLT.2.1 What is a Portal?

A portal is a web based application that –commonly- provides personalization, single

sign onauthentication, content aggregation from different sources and hosts the 5

presentation layer of Information information Systemssystems. Aggregation is the action

of integrating content from different sources within a web page. A portal may have

sophisticated personalization features to provide customized content to users. Portal

pages may have different set of portlets creating content for different users.

PLT.1.2PLT.2.2 What is a Portlet? 10

A portlet is a Java technology based web component, an application that provides a

specific piece of content (information or service) to be included as part of a portal page. It

is managed by a portlet container, that processes requests and generates dynamic content.

Portlets are used by portals as pluggable user interface components that provide a

presentation layer to Information information Systemssystems. 15

The content generated by a portlet is also called a fragment. A fragment is a piece of

markup (e.g. HTML, XHTML, WML) adhering to certain rules and can be aggregated

with other fragments to form a complete document. The content of a portlet is normally

aggregated with the content of other portlets to form the portal page. The lifecycle of a

portlet is managed by the portlet container. 20

Web clients interact with portlets via a request/response paradigm implemented by the

portal. Normally, users interact with content produced by portlets, for example by

following links or submitting forms, resulting in portlet actions being received by the

portal, which are forwarded by it to the portlets targeted by the user's interactions.

The content generated by a portlet may vary from one user to another depending on the 25

user configuration for the portlet.

This specification will deal with Portlets as Java technology based web components.

PLT.1.3PLT.2.3 What is a Portlet Container?

A portlet container runs portlets and provides them with the required runtime

environment. A portlet container contains portlets and manages their lifecycle. It also 30

Java

Portlet Specification, version 12.0 (10/07/20032007)

provides persistent storage for portlet preferences. A portlet container receives requests

from the portal to execute requests on the portlets hosted by it.

A portlet container is not responsible for aggregating the content produced by the

portlets. It is the responsibility of the portal to handle the aggregation.

A portal and a portlet container can be built together as a single component of an 5

application suite or as two separate components of a portal application.

PLT.1.4PLT.2.4 An Example

The following is a typical sequence of events, initiated when users access their portal

page:

• A client (e.g., a web browser) after being authenticated makes an HTTP request to 10

the portal

• The request is received by the portal

• The portal determines if the request contains an action targeted to any of the

portlets associated with the portal page

• If there is an action targeted to a portlet, the portal requests the portlet container to 15

invoke the portlet to process the action

• A portal invokes portlets, through the portlet container, to obtain content

fragments that can be included in the resulting portal page

• The portal aggregates the output of the portlets in the portal page and sends the

portal page back to the client 20

PLT.2.5 Compatibility

The Java Portlet Specification V 2.0 does not break binary compatibility with V 1.0. This

means that all portlets written against the V 1.0 specification can run unchanged. Portlet

V2.0 containers must support deploying JSR 168 portlets and the JSR 168 deployment

descriptor.

The only exceptions to this rule are:

• RenderResponse.setContentType is no longer required before calling getWriter

or getOutputstream. Calling getWriter or getOutputstream without previously

setting the content type results no longer in an IllegalStateException in V 2.0.

• getProtocol for included servlets / JSPs no longer returns null, but 30

‘HTTP/1.1’ in V2.0.

PLT.2.6 Major changes introduced with V 2.0

The major new features of version 2.0 include:

Java

Portlet Specification, version 12.0 (10/07/20032007)

• Events – enabling a portlet to send and receive events and perform state changes

or send further events as a result of processing an event.

• Public render parameters – allowing portlets to share parameters with other

portlets.

• Resource serving – provides the ability for a portlet to serve a resource.. 5

• Portlet filter – allowing on

-the -fly transformations of information in both the

request to and the response from a portlet .

PLT.2.6.1 Clarifications that may make V1.0 Portlets Non-

compliant

Depending on the implementation of the portlet of a specific runtime behavior of a portlet 10

container the following clarifications may lead to different results when executing a

portlet in either a JSR 168 or a JSR 286 container:

• XML escaping of portlet URLs produced via the portlet tag library.

V 2.0 clarifies that the default is all portlet URLs are XML escaped. The default

can be changed with the new attribute escapeXML. JSR 168 portlets depending on 15

the fact that portlet URLs created via the tag library are not XML escaped can

change the default to non-escaped via the portlet container runtime option

javax.portlet.escapeXml (see PLT.26.7)

• Defining multiple values for the same parameter name in the Portlet param tag.

V 2.0 clarifies that if the same name of a parameter occurs more than once within 20

an actionURL, renderURL or resourceURL the values must be delivered as

parameter value array with the values in the order of the declaration within the

URL tag. Portlets assuming that the last occurrence wins and replaces the

previous set values will behave differently in V2.0 containers.

• getProtocol for included servlets / JSPs no longer returns null. 25

V 2.0 defines that getProtocol now returns ‘HTTP/1.1’ and thus is better aligned

with the servlet model that expects the getProtocol to return this value in the

GenericServlet.

• Parameters set on the portlet URL and the post body are aggregated into the

request parameter set. Portlet URL parameters are presented before post body 30

data. JSR 168 did not define if and how post body and portlet URL parameters are

being merged. The added clarification mirrors the behavior defined in the servlet

specification for servlets.

• RenderResponse.setContentType is no longer required before calling getWriter

or getOutputstream. Calling getWriter or getOutputstream without previously 35

setting the content type will no longer result in an IllegalStateException.

PLT.2.6.2 Changes to the Programming Model

The following additions were made to the V1.0 programming model:

Java

Portlet Specification, version 12.0 (10/07/20032007)

• Use application level resource bundles instead of inline localization in the

portlet.xml.

In V1.0 the only ability to localize values on the portlet application level was

inside the portlet.xml using the xml:lang attribute. With V2.0 portlet

application developers can now provide the localized values in a resource bundle 5

and thus have the localized values in separate files instead of cluttering the

deployment descriptor.

PLT.2.6.3 List of all Changes in the Specification

This section list all changes that are not editorial in nature:

• PLT.1.4: added JAXB 2.0 reference 10

• PLT 1.8: added V2.0 Acknowledgments

• PLT 2.5: added compatibility section

• PLT 2.6: added complete section with major changes introduced with V2.0

• PLT 2.7: added JavaSE and JavaEE requirements for V2.0, now based on servlet

2.4, J2EE 1.4 and Java 5.0 and a special Java 1.4 compiled version. 15

• PLT 3.0: updated to reflect new portlet capabilities

• PLT 3.2: added section on using servlet application lifecycle listeners for portlet

applications

• PLT 4.1: added portlet section

• PLT 4.3: added section about portlets and web frameworks 20

• PLT 5.0, 5.2: added references to new lifecycle interfaces EventPortlet and

ResourceServingPortlet

• PLT 5.2.3: moved the End of Service section from end of this chapter to this place

• PLT 5.3: grouped the existing sections Portlet Definition and Portlet Entity and

Portlet Window to a new section Portlet Customization Levels 25

• PLT 5.4: added new event and resource lifecycle methods

• PLT 5.4.2: added Event Request section

• PLT 5.4.3: added reference to HTTP spec that render should be a safe operation

• PLT 5.4.4: added Resource Request section

• PLT 5.4.5.1: added Action Dispatching section 30

• PLT 5.4.5.2: added Event Dispatching section

• PLT 5.4.5.3: added Resource Serving Dispatching section

• PLT 5.4.5.4: added render mode annotation description

• PLT 6.3: added Default Event Namespace section

• PLT 6.4: added Public Render Parameter Names section 35

• PLT 6.5: added Processing Event QNames section

• PLT 6.6: added Publishing Event QNames section

• PLT 6.7: added Supported Locales section

• PLT 6.8: added Supported Container Runtime Options section

• PLT 7.1: added resource URLs and clarification that portlet URLs are only valid 40

within the current request and may not be real URLs.

剩余300页未读，继续阅读

koben

粉丝: 0
资源: 21

JavaTM Portlet Specification 2.0：Public Draft for Portlet Develo...

最新资源

JavaTM Portlet Specification 2.0：Public Draft for Portlet Develo...

山东交通学院在江西2020-2024各专业最低录取分数及位次表.pdf

西京学院在江西2020-2024各专业最低录取分数及位次表.pdf

山西师范大学在江西2020-2024各专业最低录取分数及位次表.pdf

沈阳工业大学在江西2020-2024各专业最低录取分数及位次表.pdf

基于Arduino平台的自动寻找物品设计源码

桂林学院在江西2020-2024各专业最低录取分数及位次表.pdf

西安航空学院在江西2020-2024各专业最低录取分数及位次表.pdf

基于Java的order-food-server点菜小程序后端设计源码

黑龙江工程学院在江西2020-2024各专业最低录取分数及位次表.pdf

Python爬虫框架Scrapy教程《PDF文档》

最新资源