Portlets - AI, ML, VR & more

With TN5250j, it is possible to easily integrate your host applications into your portal with full single sign-on capabilities. Here is how you can do it - Integrating iSeries Host Applications into Portals

Vignette today announced the new version of its portal. The most important highlight of this release is the adoption of standards JSR 168 & WSRP. Now Vignette can be used to consume external remote portlets for web services. Following are some of the new features - -- Enhanced out-of-the-box search capabilities that allow users to query a wide range of internal and external data sources -- Improved personalization. -- Improved & tightly integrated content management system. -- Integration with Vignette(R) Records and Documents through the use of standards-based JSR-168 portlets. Check press release here.

With the development of JSR 168, we had seen some really beautiful dreams. There will be a world where vendor neutralization will be everywhere. Anyone will be able to take portlets from one portal and will be able to deploy it in another portal. It will be as good as web application porting. And during this beautiful dream, here comes the devil – the spec violation and making so many additions to make interoperability non-interoperable. Why I am talking about my nightmare here. Isn't I am using the Weblogic workshop for a while now? What happened, have they said 'no' to sponsor some of my project? :-) Though we are using the Weblogic workshop for portlet development for quite a while, but I was not directly involved in the development. I mostly use IBM WSAD or Eclipse for JSR 168 portlet development. The real reason behind this sudden agony is that I had to deploy the portlet developed using Weblogic workshop into the WebSphere portal. First and the most interesting one - ...