Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Swordfish Documentation: ODE deployment wizard"
(→The functionality provided by the ODE depoyment project) |
(→The functionality provided by the ODE depoyment project) |
||
| Line 20: | Line 20: | ||
<li>parses wsdl files to build the http endpoint configuration</li> | <li>parses wsdl files to build the http endpoint configuration</li> | ||
<li> rebuilds bpel-exporter.xml and http-endpoints.xml files</li></ul> | <li> rebuilds bpel-exporter.xml and http-endpoints.xml files</li></ul> | ||
| + | <br> If no deploy.xml or bpel process file can be found within the project's source folders, no artifacts will be produced by the builder. If any resource tracked by the builder is changed(e.g. .wsdl files, deploy.xml or .bpel ) the artifacts will be modified correspondingly | ||
Revision as of 11:14, 4 October 2009
Creating the ODE depoyment project
Select File > New Wizard > Swordfish > ODE deployment project
Next follow the standard New Eclipse Plugin project wizard. Basically that's it
The functionality provided by the ODE depoyment project
The created ODE deployment project is the ordinary Eclipse plugin project with Java nature installed. The only difference is that this project type leverages the custom builder to create/modify ode configuration. If one opens the projects properties->builders dialog he shall see the following
br>
The OdeArtifactsProjectBuilder is responsible for creating two spring xml application context files in the META-INF/spring directory:
- bpel-exporter.xml that points to the folder containing deploy.xml and bpel process files being deployed
- http-endpoints.xml containing the configuration for the servicemix http outbound/inbound endpoints used by the bpel process
The OdeArtifactsProjectBuilder tracks changes in the project's source folders, and creates/modifies the listed configuration files.
The builder works by the following scenario:
- it scans the deploy.xml file to retrieve the partner links used in the deployed process
- examines the bpel process file to extract wsdl locations used by the partner links
- parses wsdl files to build the http endpoint configuration
- rebuilds bpel-exporter.xml and http-endpoints.xml files
If no deploy.xml or bpel process file can be found within the project's source folders, no artifacts will be produced by the builder. If any resource tracked by the builder is changed(e.g. .wsdl files, deploy.xml or .bpel ) the artifacts will be modified correspondingly