Upgrade to a portlet project


Inovke the wizard from the popup menu

Page 1 of 2

Page 2 of 2

Select the folder that should contain the web content such as jsp files, WEB-INF directory, etc. Since you are upgrading from an existing project to a protlet project, you might already have such a folder, if not then create a new one.

Once you select the web folder, the wizard provides two options. The first one will make your WEB-INF/classes the default binary folder, this is recommanded. The second option will only be enabled if you have an existing lib directory under WEB-INF, if so, then this option will add all the jar files to the classpath, if not, this option will be disabled.

Simply, the context root that should be used when deploying the portlet.

The deployment directory that this portlet application will be deployed to. For example, if you select C:\portlets\ as your deployment directory, then once you deploy the portlet project with the 'exploded' option, the deployed application will exist under c:\portlets\<your application context root>

Here you have two choices:
Exploded Archive
When you deploy your application using this option, the whole directory structure including files and subdirectories in your project's web content folder will be copied to the deployment folder under a directory with the same name as the context root that you provided earlier.
Packaged Archive
When you deploy your application using this option, a WAR file is created that contains all the files and subdirectories from your project's web content folder. The WAR file will have the same name as the context root that you provided earlier. The WAR file is then put in the deployment directory.
If you uncheck the box, then deployment files will always be overwritten. The selection you make for this checkbox only takes effect for the selected project. Each project has its own deployment overwrite option.

As part of the eXo portlet container requirement, the <display-name> element in web.xml should match the context root of the portlet application. However, you no longer need to modify this manually, it is done for you. Along with the <display-name> element, a specific <listener> element, a <servlet> element, and a <servlet-mapping> element will also be inserted so your portlet application can be identified by the eXo portlet container. The first checkbox gives you the choice of enabling the detection of a possible mismatch for any of the above elements. If you don't select this checkbox, then no attempt to detect such a mismatch will be performed, and the second checkbox will become irrelevant. However, if you do select the first checkbox, then you have the choice of enabling/disabling the prompt dialog. Please be aware that if you disable the prompt dialog, then web.xml will be modified automatically. Modifying web.xml will not preserve the existing format of the file, however, any existing comments in the web.xml file will not be lost.

The following are the exact elements that will be added if they do not exist (<display-name> element is not shown here) :
    <listener>
        <listener-class>org.exoplatform.services.portletcontainer.impl.servlet.PortletApplicationListener</listener-class>
    </listener>
    <servlet>
        <servlet-name>PortletWrapper</servlet-name>
        <servlet-class>org.exoplatform.services.portletcontainer.impl.servlet.ServletWrapper</servlet-class>
    </servlet>
    <servlet-mapping>
        <servlet-name>PortletWrapper</servlet-name>
        <url-pattern>/PortletWrapper</url-pattern>
    </servlet-mapping>
    



© Copyright The eXo Platform SARL 2000-2004.


Last updated $Date: 2004/04/19 03:37:16 $