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: BPEL with JaxWS Service"
(New page: {{#eclipseproject:rt.swordfish}} Work in progress! = Description = Provide a Swordfish -ODE Integration based on the JaxWS interface. = Current Problem / Pain = As of now only the ODE B...) |
|||
| Line 1: | Line 1: | ||
{{#eclipseproject:rt.swordfish}} | {{#eclipseproject:rt.swordfish}} | ||
| − | + | Draft | |
| − | + | ||
= Description = | = Description = | ||
| − | Provide a Swordfish -ODE Integration based on the | + | Provide a Swordfish -ODE Integration based on the JAX-WS interface. |
= Current Problem / Pain = | = Current Problem / Pain = | ||
| Line 10: | Line 9: | ||
= Advantages/Business Case = | = Advantages/Business Case = | ||
| − | + | JAX-WS Services can be Used within BPEL Processes. | |
= Use Cases = | = Use Cases = | ||
| + | Prerequisite for both scenarios: BPEL Process and JAX-WS Service Participant are deployed into separate Swordfish instances. | ||
| + | * JAX-WS Service Consumer System running in Swordfish calls a BPEL process. The BPEL process implements the Service Provider. | ||
| + | * The BPEL Process implements the Service Consumer which calls a JAX-WS Service Provider. | ||
= Conditions of satisfaction = | = Conditions of satisfaction = | ||
| − | + | Proposal: Use the Swordfish Flight Booking Example in the Demo | |
| − | + | ||
| − | Proposal: Use the Swordfish Flight Booking | + | |
| − | + | Based on the feature completeness definition (Start/Run/Control) all demo steps shall be executed within the Eclipse IDE. | |
| + | * Demonstrate Deployment | ||
| + | * Demonstrate a BPEL process where the JAX-WS Service Consumer System running in Swordfish initiates a BPEL step. | ||
| + | * Demonstrate a BPEL process where JAX-WS Service Provider running in Swordfish is invoked from a BPEL step. | ||
| + | * Integration Tests: Results for both scenarios are ok. | ||
| + | * The BPEL Example is Documented in Wiki | ||
| + | |||
| + | |||
| + | = Limitations = | ||
| + | The Documentation may be restricted to Wiki in case we have limited access to the documentation team. | ||
= Dependencies = | = Dependencies = | ||
| − | ODE | + | ODE Deployment into Swordfish was successful. |
= Non functional aspects = | = Non functional aspects = | ||
| Line 45: | Line 54: | ||
= Open Questions = | = Open Questions = | ||
| + | * Would tests results be valid, if we run the integration test of BPEL and JAX-WS participant within the Same Swordfish Instance? Which restrictions would this test scenario cause? | ||
Revision as of 05:57, 4 March 2009
{{#eclipseproject:rt.swordfish}} Draft
Contents
Description
Provide a Swordfish -ODE Integration based on the JAX-WS interface.
Current Problem / Pain
As of now only the ODE Bundle Deployment into Swordfish was acheived.
Advantages/Business Case
JAX-WS Services can be Used within BPEL Processes.
Use Cases
Prerequisite for both scenarios: BPEL Process and JAX-WS Service Participant are deployed into separate Swordfish instances.
- JAX-WS Service Consumer System running in Swordfish calls a BPEL process. The BPEL process implements the Service Provider.
- The BPEL Process implements the Service Consumer which calls a JAX-WS Service Provider.
Conditions of satisfaction
Proposal: Use the Swordfish Flight Booking Example in the Demo
Based on the feature completeness definition (Start/Run/Control) all demo steps shall be executed within the Eclipse IDE.
- Demonstrate Deployment
- Demonstrate a BPEL process where the JAX-WS Service Consumer System running in Swordfish initiates a BPEL step.
- Demonstrate a BPEL process where JAX-WS Service Provider running in Swordfish is invoked from a BPEL step.
- Integration Tests: Results for both scenarios are ok.
- The BPEL Example is Documented in Wiki
Limitations
The Documentation may be restricted to Wiki in case we have limited access to the documentation team.
Dependencies
ODE Deployment into Swordfish was successful.
Non functional aspects
Volume / Load aspects
Security aspects
Authentication should be supported, which requires the ability to propagate policies.
Ease of Use
Architecture Outline/ Implementation Ideas
Open Questions
- Would tests results be valid, if we run the integration test of BPEL and JAX-WS participant within the Same Swordfish Instance? Which restrictions would this test scenario cause?
Return to Eclipse Swordfish Swordfish Product Backlog