eXo Platform WebUnit Test
You can now run eXo Platform webunit groovy testsuites within Eclipse. Once you have the appropriate project structure for eXo Platform webunit tests, invoke the action from the popup menu by right clicking on the file. A browser window will appear, and you can execute each test step by step or all at once. |
![]() |
eXo Platform Launch Configuration
You can now create an eXo Platform launch configuration by simply providing the location of the eXo Platform binary distribution, and the location of the eXo Platform source code (optional - and no need to compile eXo platform source code). |
![]() |
Start/Stop eXo Platform
Once you create an eXo Platform launch configuration, you can start/stop eXo Platform from Eclipse using the toolbar buttons. Or, if you prefere you can use the default shortcut keys to start/stop eXo Platform. The shortcut keys to start eXo Platform are Ctrl+Shift+F11, and the shortcut keys to stop eXo platform are Ctrl+Shift+F12. |
![]() ![]() |
Deploy Portlet action
You can access this action either via the menu bar or by using the default key shortcut (Ctrl+Shift+F10). This action takes care of packaging the portlet project and copying the result to the deployment directory. |
![]() |
Portlet Deployment Descriptor Validation
You can now validate portlet.xml and see the errors as markers. You have the choice of automatically validating portlet.xml and/or performing validation manually by choosing the 'Validate Portlet Deployment Descriptor' option from the popup menu. |
![]() ![]() |
Upgrade a Java Project to a Portlet Project
Use the upgrade wizard to upgrade your existing Java project to a portlet project. To
access the upgrade wizard, first select the project from the 'Package Explorer' view, and then
find the upgrade option in the pop up menu (right click the mouse). |
![]() ![]() |
Decoration of Portlet Projects
You can now easily identify a portlet project, its web-folder, its context root, and the JSR 168 version used by its portlet deployment descriptor. |
![]() ![]() |
Automatically modify web.xml to include the correct context root value
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. |
![]() ![]() |
eXo Portlet Settings Property Page
For each portlet project, the plugin provides a property page that contains information related to deployment, such as the context root and the deployment directory. The information presented in this page is used later by the Deploy Portlet action. |
![]() |
A portlet project wizard
This wizard creates a project with all the essential files and directories structure that are common among any portlet project. You also can specify the source folder name, the name of the folder that contains the web content (such as jsp files), and the context root to use when deploying the application. One feature that we particularly like is the ability to start with a sample project. Currently, the wizard comes with one sample application (you guessed it, it is a HelloWorld sample). However, expect to see much more interesting sample projects in future releases of the plugin. |
![]() ![]() ![]() |
© Copyright The eXo Platform SARL 2000-2004.
Last updated $Date: 2004/10/11 01:11:31 $