Embedding Pluto 2

[James Cook <jc...@tracermedia.com>]

I have integrated the Pluto Portlet Driver in my web application, and setup
a Spring context which mimics the config that ships with Pluto.

I am at the point where I need to embed a portlet in my web application, and
I am confused over the next steps.

I don't want to give the user any control over where the portlets appear and
how they are configured. I just want to hardcode portlets into particular
spots in the web app. One of the config files I had to set up is the
pluto-portal-driver-config.xml file. This file has the render-config
section:

    <render-config default="About Apache Pluto">
        <page name="About Apache Pluto"
uri="/WEB-INF/themes/pluto-default-theme.jsp">
            <portlet context="/pluto" name="AboutPortlet"/>
            <portlet context="/testsuite" name="TestPortlet1"/>
        </page>
        <page name="Test Page"
uri="/WEB-INF/themes/pluto-default-theme.jsp">
            <portlet context="/testsuite" name="TestPortlet1"/>
            <portlet context="/testsuite" name="TestPortlet2"/>
        </page>
        <page name="JSR 286 Tests"
uri="/WEB-INF/themes/pluto-default-theme.jsp">
            <portlet context="/testsuite" name="286TestPortlet"/>
            <portlet context="/testsuite" name="286TestCompanionPortlet"/>
        </page>
        <page name="Pluto Admin"
uri="/WEB-INF/themes/pluto-default-theme.jsp">
            <portlet context="/pluto" name="PlutoPageAdmin"/>
            <portlet context="/pluto" name="AboutPortlet"/>
        </page>
    </render-config>

If the portlet driver requires the setup of this information I fear I am
barking up the wrong tree. Based on my use case, I shouldn't be setting up
pages or specifying which portlets reside on each page.

Should I be looking into embedding the portlet container and not the portlet
driver?

-- jim