Hi all

I'm wondering what's necessary to create a Portal of my own with
pluto-1.1. I've gone trough the pluto-portal.war and
pluto-testsuite.war and my impression is this:

Some libraries must be in TOMCAT/shared/lib (like portlet-api,
pluto-descriptor and a few others). What's the reason for this?
Generally, I'd rather deploy all libs as part of the webapp war. Also,
I'm wondering about the files being copied to
TOMCAT/conf/Catalina/localhost - they're not that important since
tomcat should pick up the war files by himself, shouldn't he?

The files pluto-portal-driver*.xml work somewhat like the web.xml.
They mark a webapp as portal and if they are present, the
portal-driver picks up the webapp (probably after it's been deployed
by tomcat) and initializes the portal.

As it seems to me, at the moment, the portlet.xml is a marker file too
and is only relevant to the portlet container. I assume, tomcat loads
and initializes the webapp (servlets) and then calls the portlet
container to initialize the portlets. How does tomcat know about the
portlet container?

I home someone can clear this up so I get a better understanding of
the pluto architecture.

Thanks
Patrick

Reply via email to