Portlet and Portal Development Best Practices

As we have doing some research on the Portal development ... i found sometime is useful to share with all other involve on the portal / portlet development...

Here are some of the best pratices

1. Don't Use PortletPreferences
When you store information in the PortletPreferences object, you are giving up control over where the data is stored, how the data is stored, and how easy it is to potentially mine that data in the future. That's a whole lot of control to be giving up.

2. Get Service Oriented
Don't try to do too much in your portlets. Behavior coded into one portlet is very difficult to reuse in another portlet. Instead, factor our useful and potentially common behavior into a service layer.Making a portlet too complex can slow down the portal, and create a frustrating experience for the user.

3. Encode Your NameSpaces
To avoid name collisions on the portal server, all scripts, URLs, HTML form attributes, and the like, should be namespace encoded. Without encoding a namespace, your portlets will likely work properly in a sequestered, local test environment, but may encounter some very obscure and difficult to reproduce errors when your portlets go into production.

Others:
Use Good Variable Names
Minimize Session Bloat
Comment Your Friggin' Code
Handle IO Exceptions
Servlet and JSP Rules Apply
Use the expiration-cache Tag
Not Every Portlet is a Framework Portlet

Some Cool Stuff to Share

1. GWT-Ext UI Tools for web

Click GWT-Ext

2. Gilead stands for Generic Light Entity Adapter

Click Gilead

3. Desktop Look A like EXTJS

Click EXTJS