Skip to main content

Pros and Cons of Portal technology

Portal Technology came with lot of promises. Many companies started migrating from normal web based application to portal technologies in no time within last couple of years.
Why there was so much like for Commercial and Open Source Portals?

Few Services the Portals where providing out of the box
  1. Displaying large amount of information in a single page
  2. Information can be fragmented into simple small windows which can be placed anywhere on the page
  3. A particular window has two modes View and Edit. View is the default for displaying information and edit is used to for editing the information.
  4. Developers in a team can work on any particular portlet ( window) without interfering with other developers work
  5. Portals provide security, look and feel out of the box and everything is dynamically updatable.
Couple of Big drawbacks of Portal Technlogy

Reason:
  1. Bandwidth: this is one big drawback all the portals which are available in the market rendering, refreshing, every request to server yields to consume lot of bandwidth on an average of 200KB.
  2. Slow: Updating one portlet results in updating all the other portlets with normal http request and response.
However there is lot of push in using Ajax for request and response on portals which will bring the technology to live and will compete with RIA's
Example of Portals which uses Ajax or Support Ajax is LightPortal, Sun Portal etc

Comments

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">         <

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

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