Portals Bridges
  1. Portals Bridges
  2. PB-30

Documentation of Configuration in Pluto


    • Type: New Feature New Feature
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 0.3
    • Fix Version/s: None
    • Component/s: struts
    • Labels:
    • Environment:
      Pluto 1.0.1 / Tomcat 5.5.9


      I got the Pluto / Struts connection working. It is a little bit tricky.

      As we already discussed, all mappings have to begin with a /. I am not sure if this is a limitation in Pluto.

      There need to be two servlets in web.xml. The first servlet is basically a servlet to run the struts portlet. All portlet based actions must run through this servlet. The portlet-class is the StrutsPortlet class and the portlet-guid is configured in the particular portlet container config files. I will give you our example later.

      <display-name>StrutsPortlet Wrapper</display-name>
      <description>Struts Action Wrapper</description>

      The second servlet is the struts-bridge PortletServet servlet with the standard struts params.

      <display-name>Struts Portlet Servlet</display-name>

      The servlet mapping is the tricky part. Anything running through the portlet container needs to map to the Portlet Servlet (ctp stands for ClienTracPortlet).


      The struts action mapping is used to find the struts action servlet. This will be referenced below. (cta stands for ClienTracAction).


      The portlet.xml file must reference the struts action in the ViewPage (or edit, help pages). It is using your servlet context provider and the /cta/* mapping.
      the /cta mapping would also be used in login.jsp. I have to run some tests to determine the format of the action url's in struts jsp files.

      <description>ClienTrac Rental Real-Estate Tracking System</description>
      <display-name>ClienTrac Rental Real-Estate Tracking System</display-name>

      In pluto there are three files which determine the portlet configuration.

      The lead file is portletcontents.txt. This is a list of contexts which have registered portlets.


      Next is the pageregistry.xml. This determines the initial layout of the page of portlets. You will see references in the log to
      row_col1_p3 as this is key to access the portlet. The 7.0 is the link to the portletentityregistry.xml

      <fragment name="clientrac" type="page">
      <description>Real Estate Rental Sales Tracking</description>
      <fragment name="row" type="row">
      <fragment name="col1" type="column">
      <fragment name="p3" type="portlet">
      <property name="portlet" value="7.0"/>

      The last file is the portletentityregistry.xml. This is a full list of the portlets available to run. The definition ID is the link back to web.xml PortletServlet. Each application is made up of portlets with the pageregistry finding the portlet by the <appliction-id>.<portlet-id> reference. The definition-id is used to find which PortletServlet to run, i.e. the portlet-guid, defined in web.xml.

      <application id="7">
      <portlet id="0">



          • Assignee:
            Edgar P. Dollin
          • Votes:
            0 Vote for this issue
            0 Start watching this issue


            • Created: