I'm working on upgrading uPortal to Pluto 2.0 and had a question about
how the code is split up. The embedding documentation and what I know
about Pluto implies that a full portal shouldn't need to depend on
anything from the pluto-portal-driver JAR. That said it seems like a lot
of the default implementations of the core Pluto services live in the
JAR, most critically PortletInvokerServiceImpl which seems onerous for a
portal to re-implement since its functionality is tightly coupled to the
portlet invoking servlet.
Is the intent that portals embedding Pluto reference code from
pluto-portal-driver or should some of these default service
implementations be moved into the container impl?
-Eric
|