Skip to main content

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.

Jump to: navigation, search

Difference between revisions of "Swordfish Documentation: Galileo Sprint1"

m (Code generation based on JAX-WS reference implementation)
m (Code generation based on JAX-WS reference implementation)
Line 47: Line 47:
 
===Code generation based on JAX-WS reference implementation ===
 
===Code generation based on JAX-WS reference implementation ===
 
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.
 
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 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)

Revision as of 03:36, 5 March 2009

{{#eclipseproject:rt.swordfish}}

Sprint Goals

  1. Creating ORBIT projects.
  2. Integrate Apache CXF
  3. Integrate ODE 2.0 Beta into Servicemix 4
  4. JaxWS Service integration with ODE
  5. Service Registry REST interface: Prototype for lookup
  6. Code generation based on JAX-WS reference implementation
  7. Logging Event Sink


Sprint Activities

Sprint Activities

Demo Scope

Creating ORBIT projects.

  • Show a status list for all filed the CQ's for the orbit.

Integrate Apache CXF

  • Show internal documentation on how to deploy JBI endpoints without JBI packaging
  • Demonstrate a "Hello-Swordfish" roundtrip (http, request response) in loop back mode (Consumer and Provider in Same OSGi).
  • QA: Show how to set up and run a prototype integration test for the above example in a development environment.

Integrate Apache ODE 2.0 Beta into Apache Servicemix 4

  • Show internal documentation on steps required to manualy build Apache ODE OSGi Bundle and to deploy it into Swordfish
  • show proposal for deployment scenario alternatives with pros and cons
  • Run one Apache ODE Example in Swordfish

JaxWS Service integration with Apache ODE

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

  • Demonstrate a successful lookup with the prototype (can be executed against file system or existing registry)
  • Demonstrate a basic negative scenario: No matching provider found
  • Show Initial Documentation:
    • 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.

As this is a prototype: no installation requirement yet.

Code generation based on JAX-WS reference implementation

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

Create and Show a log for one successful and one failed service call.

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.

Return to Eclipse Swordfish Sprint Planning

Swordfish Dokumentation Home

Back to the top