I am not sure the rest, but I could give you some info about IBM's WSRP. In the existing portal applications (expecially for remote invocation), we need to write our own codes to cater this requirement.
However, IBM's WSRP (I guess it should be the same for WSRP-4j), namely Web Services for Remote Portal, provides a standard interface for remote portlets communication via Web Services. Thus, it could save us some coding effort. However, IBM's WSRP is still in the stage of preview. I guess Apache might already finish it.
How are diferent between Apache Pluto and Apache JetSpeed
In IBM's terminology (I am not sure whether it is in fact a generic term), JetSpeed should be the 1st/2nd generation of portlet, while Pluto is the 3rd/4th generation of portlet. The supported levels of each is different, and now, upto the 4th generation, we got a user-friendly (or should be a developer-friendly) portlets to do the web info aggregation.
Originally posted by somkiat puisungnoen: How are diferent between Apache Pluto and Apache JetSpeed , WSRP-4j ?[/QB]
Pluto is a JSR168 Portlet engine.
JetSpeed is a Portlet Server, in fact JetSpeed 2(still under develope) is using Pluto as its Portlet Engine.(JS1.x is not JSR168 compliant, it use its own engine and different API)
WSRP-4j(donated by IBM) is the Apache's implementation of WSRP Protocol which make different portal Engines can remotely call others portlet using Web Service. [ November 11, 2004: Message edited by: Martin CHOW ]
WSRP is OASIS Specification, not from JCP. somewhat like UDDI, WSRP defined the API, but not limited to one language. WSRP4J, like UDDI4j, implement the API in Java. (I'm not sure, but I think JCP haven't JSR for WSRP. maybe SUN will make it's own API for WSRP in future, just like SUN make JAXR for UDDI) [ November 11, 2004: Message edited by: Martin CHOW ]
You showed up just in time for the waffles! And this tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop