JSR 168 Portlet Development Guidelines

Drew Varner, Sr. Pricipal Consultant at BEA, has written a good post on JSR 168 portlet development guidelines. These are some basic guidelines that a portlet developers must aware of. He has also given examples to support his views. Here are the guidelines -

1. Always Utilize the URL Rewriting APIs for Content in Your Portlet
2. Do Not Append Paths to a Rewritten URL
3. Qualify Client-side Script Variables and Methods with Namespaces
4. Ensure Inline Client-side Scripts that Refer to Portlet Resources Follow the Spec
5. Always Declare a Content Type for Portlet Responses
6. Do Not Send Cookies from Portlets
7. Separate Business Logic from Presentation

Please check his post for details.

Comments

Post a Comment

Popular posts from this blog

Web Clipping for Portals goes Mainstream

Lack of good web clippers (aka URL scrappers) in the market obstructs quick portal adoption. Web Clipping is one of the fastest methods for integrating existing applications with the portals. Though nearly all portals come with web clipper tools/ portlets but most of them lack the professional touch. Kapow and Clickmarks are two such companies in the market whose products are quite advanced in comparison to out-of-box web clipping portlets provided with most portals. Yesterday's announcement by Kapow Technology for the release of version 6.0 of "RoboSuite Web Integration platform" will definitely boost this market. Kapow Press Release
Read more

Firebase upgraded properties are not yet supported in Google Analytics App

Image
Recently I saw a message in Firebase Console to upgrade my Firebase property to Google Analytics property. Such properties are called Google Analytics App + Web properties in GA after upgrade. The primary benefit for upgrading the property that I see is that we can see all Firebase Analytics data in Google Analytics. Google Analytics is a tool that we all have used for years and it is slightly easier for me. I am also more comfortable doing analysis using Google Analytics than Firebase Analytics. On top of that we also get benefit of third party integrations like AdWords (now Google Ads) integration if we get all the data from Firebase Analytics into Google Analytics. So, I upgraded my Firebase property to Google Analytics property. The was a pleasant experience to see all Firebase Analytics data in Google Analytics in the format that I understand much better. But soon I realized that there is one important part missing. On The Go, I use Google Analytics App to get a quick glance of
Read more

One more JSR 168 Compliant Product

It looks that now the JSR 168 compliant products are flooding. There are many commercial and open-source already compliant and new products are joining day by day. This time it is the turn of saba . I have not seen/used this product so I am not sure what exactly is the product. One thing is sure that it is not a complete portals solution. They call it "human capital development and management (HCDM)" solution. Anyway it is a good news for whole java portal world. Press note say that the human capital development and management (HCDM) solutions provider company saba , announced that it will support the Java Specification Request 168 (JSR 168) portlet standard (also called portlet 1.0) in its next-generation platform offering integrated performance and learning solutions for large-scale, enterprise-wide deployments. Please check the complete news release here.
Read more