Skip to main content

JSR-168 Specification / Portal Architecture



The Portlet Specification addresses the following topics

  1. The portlet container contract 
  2. Portlet life cycle management
  3. The definition of window states
  4.  Portlet modes
  5.  Portlet preferences management
  6.  User information
  7.  Packaging and deployment
  8.  Security 
  9.  JSP tags to aid portlet development



Container Contract
The life cycle methods called directly by the container are:

  • init() 
  • destroy() 
  • processAction() 
  • render() 

In addition to the methods above, which are called directly by the container, a GenericPortlet class is provided
that implements the render() method and delegates the call to more specific methods to display the portlet based
on its mode. Developers can extend GenericPortlet and implement as many of these specialized render methods as
are necessary for their portlet. These methods are: Called by render()
doView()
doEdit()
doHelp()

Portlet Preferences
as a persistent set of name-value pairs and are referred to as portlet preferences.
the getValues() and setValues() methods respectively.
Portlets have access to the PortletPreferences object when processing requests, but may only modify preference attributes during a processAction invocation. Prior to the end of the processAction method, the store()


JSP Tag Library
A JSP Tag library is included to help display portlet pages with JSP technology. For example, a custom JSP tag
automatically declares the portlet request and response objects so they can be used within the JSP. Another JSP tag
helps construct URL’s that refer back to the portlet.

Reference
http://developers.sun.com/portalserver/reference/techart/jsr168/pb_whitepaper.pdf

Comments

Post a Comment

Popular posts from this blog

Access multiple Databases in JPA

According to JPA specification we can define multiple "persistence-unit" elements (i.e. like below) in persistence.xml file and can easily refer them inside Dao layers as this. public class PolarDaoImpl {     @PersistenceContext(unitName="PolarPU")     protected EntityManager entityManager; -- } public class BearDaoImpl {     @PersistenceContext(unitName="BearPU")     protected EntityManager entityManager; -- } Checkout sample persistence.xml <?xml version="1.0" encoding="UTF-8"?> <persistence version="2.0" xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_2_0.xsd">     <!-- Database 1 -->     <persistence-unit name="PolarPU" transaction-type="RESOURCE_LOCAL">         <
3 comments
Read more

JPA 2 new feature @ElementCollection explained

@ElementCollection is new annotation introduced in JPA 2.0, This will help us get rid of One-Many and Many-One shitty syntax. Example 1: Stores list of Strings in an Entity @Entity public class Users implements Serializable {     private static final long serialVersionUID = 1L;     @Id     @GeneratedValue(strategy = GenerationType.AUTO)     private Long id;     @ElementCollection     private List<String> certifications = new ArrayList <String> ();     public Long getId() {         return id;     }     public void setId(Long id) {         this.id = id;     }     public List <String> getCertifications() {         return certifications;     }     public void setCertifications(List <String> certifications) {         this.certifications = certifications;     } .. }         Users u = new Users();         u.getCertifications().add("Sun Certified Java Programmer");         em.persist(u); Generated Tables    Users    Co
21 comments
Read more

Reuse JPA Entities as DTO

Note : Major design advantages of JPA Entities are they can detached and used across tiers and networks and later can by merged. Checkout this new way of querying entities in JPA 2.0 String ql = " SELECT new prepclass2.Employee (e.firstname, e.lastname) FROM Employee e "; List<Employee> dtos = em.createQuery(ql).getResultList(); The above query loads all Employee entities but with subset of data i.e. firstname, lastname. Employee entity looks like this. @Entity @Table(name="emp") public class Employee implements Serializable {     private static final long serialVersionUID = 1L;     @Id     @GeneratedValue(strategy = GenerationType.AUTO)     private Long id;     @Column     private String firstname;     @Column     private String lastname;     @Column     private String username;     @Column     private String street;     @Column     private String city;     @Column     private String state;     @Column     private String zipc
11 comments
Read more