Difference between revisions of "EDT:Deployment Introduction"
m (→Imports & Resources:)
m (→Some Tips of Deployment)
|Line 51:||Line 51:|
= Some Tips of Deployment =
= Some Tips of Deployment =
If you are using Java external types in your projects, you should have configured the Java build path of your EGL project to make sure there are no compile errors
If you are using Java external types in your projects, you should have configured the Java build path of your EGL project to make sure there are no compile errors generated Java code. But when you deploy the EGL project to the target project, the external JAR can not be deployed to the target project. You need to modify the Java build path again in the target project manually.
Revision as of 13:02, 20 February 2012
Deployment Descriptor File
There will be a deployment descriptor (DD for short) file in each EGL project you have created. As we introduced in the last section, an EDT deployment operation is needed if you are writing an EGL project with a handler or service. The DD file maintains all of the information needed for deployment. The following section will introduce the details of this.
The DD file will be created automatically when you create any of the EGL project types in EDT. It will be placed in the EGLSource folder with the same name as your project. Although RUIHandler and service deployment be will added to DD file automatically when you use the creation wizard, there are still some settings which will need your manual modification. See the points listed below.
This tab shows all of the status of the details tabs. You can switch to a specific tab by clicking Details or by double-clicking on the item in the grid.
The Target Project combo box lists all dynamic web projects in the current workspace. You should select one of the projects, or create a new one. When doing deployment, this field can not be empty.
Rich UI and Service Deployment:
One of the main purposes for the DD file is to deploy Rich UI Handlers and REST services to the target project. These two types of EGL files will be added to the DD file by default when you create them with the creation wizard.
You can manually modify the Rich UI Handlers and services you want to deploy in these two tabs.
In the Service Deployment tab, all of the REST services you have created will be listed in the table. If you forgot to check the option Create as Web Services when creating your services, you can modify them in this tab. Just click the Add button at the right of the table. The Add Web Services wizard will pop up, and you can manage the services in this window. When your configuration is complete, click Finish to accept it.
The Resource Binding tab configures the database resources or deployed REST services you may want to use in this project. If the project contains database logic, EGL REST services, or non-EGL service invocations, you may use these tabs to configure these settings.
For details of Resource Binding, see Resource Binding Introduction.
Imports & Resources:
The Imports tab allows you to reference another DD file in a different project to reuse some of the settings. It can make your project structure more clear. For example, suppose you have two EGL projects, where the first one includes all Rich UI Handlers, and the other one includes all services. Then when you deploy the Rich UI Handler project, you can simply import the project that contains your services. This can reduce redundancy and provide better consistency.
There are two way to trigger a deployment operation. You can trigger it by right-clicking on the DD file to bring up the context menu, and then selecting Deploy EGL Descriptor; or by clicking this button at the top right of the DD file editor view. If the target project of the DD file is empty, there will be an alert notifying you to modify it. You will also see an alert if no Rich UI Handler or service deployment has been added in the DD file.
Some Tips of Deployment
If you are using Java external types in your projects, you should have configured the Java build path of your EGL project to make sure there are no compile errors in the generated Java code. But when you deploy the EGL project to the target project, the external JAR can not be deployed to the target project. You need to modify the Java build path again in the target project manually.