Thomas,uPortal 2.6 uses Pluto 1.0 and WSRP4j 0.3 (according to the uPortal docs at least) to provide portlet and WSRP consumer support.
uPortal 3.0 uses Pluto 1.1 which precludes using the same WSRP4j code that was used in 2.6 since it depends directly on Pluto 1.0. Having a WSRP4j consumer that runs in a Pluto 1.1 container is exactly what we need to be able to use it in uPortal 3.0. What would be even better is a WSRP4j consumer that is a plain-old JSR-168 portlet and doesn't rely on anything special from Pluto but honestly I don't know enough about WSRP consumption to know if that is reasonable.
uPortal 3.0 'customizes' Pluto by implementing most of the service provider interfaces that Pluto exposes but this shouldn't affect if a portlet runs in the Pluto driver (there simple test portal) or uPortal.
Most of this is summarized here as well: http://www.ja-sig.org/wiki/display/UPC/uPortal+Architecture+Overview -Eric Thomas S. Pangborn wrote:
Does uPortal use Pluto and WSRP as base libraries for handling JSR-168 and WSRP 1.0 respectively? If so would the current work on WSRP4J moving to Pluto 1.1 allow this to more easily be added to uPortal? If not which parts of uPortal are project specific? i.e. Is there a customized JSR-168 library?Thomas -- You are currently subscribed to [email protected] as: [EMAIL PROTECTED] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/uportal-dev
smime.p7s
Description: S/MIME Cryptographic Signature
