Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Swordfish Documentation: Galileo Sprint1"
m (→Demo Scope) |
|||
| (13 intermediate revisions by the same user not shown) | |||
| Line 19: | Line 19: | ||
=== Creating ORBIT projects. === | === Creating ORBIT projects. === | ||
| − | * Show the | + | <font b color=green><b> Ok </b></font> |
| + | * Show a status list for all filed the CQ's for the orbit. | ||
| − | === Integrate Apache CXF === | + | === Integrate Apache CXF === |
| − | * Show internal documentation on how to deploy JBI endpoints without JBI packaging | + | <font b color=#FFCC33><b> Roundtrip Ok, but not documented and unclear test status </b></font> |
| − | * Demonstrate a "Hello-Swordfish" roundtrip (http, request response) in loop back mode (Consumer and Provider in Same OSGi). | + | * Show internal documentation on how to deploy JBI endpoints without JBI packaging. <font b color=red><b> X </b></font> |
| − | * | + | * Demonstrate a "Hello-Swordfish" roundtrip (http, request response) in loop back mode (Consumer and Provider in Same OSGi). <font b color=green><b> Ok </b></font> |
| + | * QA: Show how to set up and run a prototype integration test for the above example in a development environment. <font b color=green><b> Was replaced through improvement/reimplementation of integration tests for configuration. </b></font> | ||
| − | === Integrate Apache ODE 2.0 Beta into Apache Servicemix 4 === | + | === Integrate Apache ODE 2.0 Beta into Apache Servicemix 4 === |
| − | * Show internal documentation on steps required to | + | <font b color=green><b> Ok, although documentation missing </b></font> |
| − | * show proposal for deployment | + | * Show internal documentation on steps required to manually build Apache ODE OSGi Bundle and to deploy it into Swordfish. <font b color=red><b> X </b></font> |
| − | * Run one Apache ODE Example in Swordfish | + | * show proposal for deployment scenario alternatives with pros and cons <font b color=green><b> Ok </b></font> |
| + | * Run one Apache ODE Example in Swordfish <font b color=green><b> Ok </b></font> | ||
=== JaxWS Service integration with Apache ODE === | === JaxWS Service integration with Apache ODE === | ||
| − | Due to reduced Team Member availability this Backlog Item | + | <font b color=red><b> Missing </b></font> |
| − | * Demonstrate | + | |
| − | * Demonstrate | + | Due to reduced Team Member availability either this or Backlog Item "Code generation based on JAX-WS" might be dropped from the sprint scope. |
| + | * Demonstrate a BPEL process where JaxWS Service Consumer running in Swordfish initiates a BPEL step. | ||
| + | * Demonstrate a BPEL process where JaxWS Service Provider running in Swordfish is invoked from a BPEL step. | ||
=== [[Swordfish_Documentation:_Registry_Feature | Service Registry REST interface: Prototype for lookup ]]=== | === [[Swordfish_Documentation:_Registry_Feature | Service Registry REST interface: Prototype for lookup ]]=== | ||
| − | * Demonstrate a successful lookup with the prototype (can be executed against file system or existing registry) | + | <font b color=green><b> Ok, includes even local and remote lookup directly and out of swordfish. </b></font> |
| − | * Demonstrate a basic negative scenario: No matching provider found | + | * Demonstrate a successful lookup with the prototype (can be executed against file system or existing registry). <font b color=green><b> Ok </b></font> |
| − | * Show Initial Documentation: | + | * Demonstrate a basic negative scenario: No matching provider found. <font b color=green><b> Ok </b></font> |
| − | ** Message definitions for Request, Response and Fault for the lookup | + | * Show Initial Documentation: <font b color=green><b> Ok </b></font> |
| − | ** Initial Java Doc for the method LookUp of the REST API (known limitation: Is still subject to change) | + | ** Message definitions for Request, Response and Fault for the lookup. |
| − | * | + | ** Initial Java Doc for the method LookUp of the REST API (known limitation: Is still subject to change). |
| − | + | * QA: Present a proposal or example on how mocks for this service registry lookup could be realized based on EasyMock. <font b color=red><b> X </b></font> | |
As this is a prototype: no installation requirement yet. | As this is a prototype: no installation requirement yet. | ||
===Code generation based on JAX-WS reference implementation === | ===Code generation based on JAX-WS reference implementation === | ||
| − | * | + | <font b color=red><b> Missing </b></font> |
| + | |||
| + | Due to reduced Team Member availability either this or Backlog Item "JAX-WS Service integration with Apache ODE" might be dropped from the sprint scope. | ||
| + | * Demonstrate the "Deployment Configuration"? Editor | ||
* Demonstrate deployment of Jax-WS based "Hello-Swordfish" Participant OSGi bundle into swordfish | * Demonstrate deployment of Jax-WS based "Hello-Swordfish" Participant OSGi bundle into swordfish | ||
* Demonstrate a "Hello-Swordfish" roundtrip of generated participants (http, request response) | * Demonstrate a "Hello-Swordfish" roundtrip of generated participants (http, request response) | ||
===Logging Event Sink === | ===Logging Event Sink === | ||
| + | <font b color=green><b> Ok </b></font> | ||
Create and Show a log for one successful and one failed service call. | Create and Show a log for one successful and one failed service call. | ||
=== QA === | === QA === | ||
| − | * Show the Unit Test Coverage Reports on the Maven Site for the Swordfish projects. Expectation: All New Projects have 80% line- and branch coverage. | + | <font b color=#FFCC33><b> Not yet set up, SR not yet transferred to Repository. Coverage remains still unclear. But good progress regarding continuous integration build. </b></font> |
| + | * Show the Unit Test Coverage Reports on the Maven Site for the Swordfish projects. Expectation: All New Projects have 80% line- and branch coverage. | ||
| + | |||
| + | ---------------------------- | ||
| + | Return to Eclipse Swordfish [[Swordfish_Documentation:_Sprint_Plan | Sprint Planning]] | ||
| + | |||
| + | [[Swordfish | Swordfish Wiki Home]] | ||
Latest revision as of 08:04, 27 March 2009
{{#eclipseproject:rt.swordfish}}
Contents
- 1 Sprint Goals
- 2 Sprint Activities
- 3 Demo Scope
- 3.1 Creating ORBIT projects.
- 3.2 Integrate Apache CXF
- 3.3 Integrate Apache ODE 2.0 Beta into Apache Servicemix 4
- 3.4 JaxWS Service integration with Apache ODE
- 3.5 Service Registry REST interface: Prototype for lookup
- 3.6 Code generation based on JAX-WS reference implementation
- 3.7 Logging Event Sink
- 3.8 QA
Sprint Goals
- Creating ORBIT projects.
- Integrate Apache CXF
- Integrate ODE 2.0 Beta into Servicemix 4
- JaxWS Service integration with ODE
- Service Registry REST interface: Prototype for lookup
- Code generation based on JAX-WS reference implementation
- Logging Event Sink
Sprint Activities
Demo Scope
Creating ORBIT projects.
Ok
- Show a status list for all filed the CQ's for the orbit.
Integrate Apache CXF
Roundtrip Ok, but not documented and unclear test status
- Show internal documentation on how to deploy JBI endpoints without JBI packaging. X
- Demonstrate a "Hello-Swordfish" roundtrip (http, request response) in loop back mode (Consumer and Provider in Same OSGi). Ok
- QA: Show how to set up and run a prototype integration test for the above example in a development environment. Was replaced through improvement/reimplementation of integration tests for configuration.
Integrate Apache ODE 2.0 Beta into Apache Servicemix 4
Ok, although documentation missing
- Show internal documentation on steps required to manually build Apache ODE OSGi Bundle and to deploy it into Swordfish. X
- show proposal for deployment scenario alternatives with pros and cons Ok
- Run one Apache ODE Example in Swordfish Ok
JaxWS Service integration with Apache ODE
Missing
Due to reduced Team Member availability either this or Backlog Item "Code generation based on JAX-WS" might be dropped from the sprint scope.
- Demonstrate a BPEL process where JaxWS Service Consumer running in Swordfish initiates a BPEL step.
- Demonstrate a BPEL process where JaxWS Service Provider running in Swordfish is invoked from a BPEL step.
Service Registry REST interface: Prototype for lookup
Ok, includes even local and remote lookup directly and out of swordfish.
- Demonstrate a successful lookup with the prototype (can be executed against file system or existing registry). Ok
- Demonstrate a basic negative scenario: No matching provider found. Ok
- Show Initial Documentation: Ok
- Message definitions for Request, Response and Fault for the lookup.
- Initial Java Doc for the method LookUp of the REST API (known limitation: Is still subject to change).
- QA: Present a proposal or example on how mocks for this service registry lookup could be realized based on EasyMock. X
As this is a prototype: no installation requirement yet.
Code generation based on JAX-WS reference implementation
Missing
Due to reduced Team Member availability either this or Backlog Item "JAX-WS Service integration with Apache ODE" might be dropped from the sprint scope.
- Demonstrate the "Deployment Configuration"? Editor
- Demonstrate deployment of Jax-WS based "Hello-Swordfish" Participant OSGi bundle into swordfish
- Demonstrate a "Hello-Swordfish" roundtrip of generated participants (http, request response)
Logging Event Sink
Ok Create and Show a log for one successful and one failed service call.
QA
Not yet set up, SR not yet transferred to Repository. Coverage remains still unclear. But good progress regarding continuous integration build.
- Show the Unit Test Coverage Reports on the Maven Site for the Swordfish projects. Expectation: All New Projects have 80% line- and branch coverage.
Return to Eclipse Swordfish Sprint Planning