Sabbu Allamaraju

JSR 168 has changed the playing field for portal development, letting vendors (and especially ISVs) develop portlets that various portals can consume. Likewise, WSRP has provided a standard so portals can consume portlets that reside remotely from the consuming portal. But questions remain. How real is the interoperability between portlets across different portal vendors? How does WSRP relate to other development patterns such as Struts and JSF? When should you use WSRP as opposed to JSR 168? As a developer developing for a portal customer, how do you know where to start? This article will discuss two approaches to deploying portlets: the use of Java Specification Request (JSR) 168, which addresses the characteristics and specifications for a Java portlet, and the specification for Web Services for Remote Portlets (WSRP) from OASIS, one of the industry organizations ... (more)