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: Galileo Sprint2"
| Line 20: | Line 20: | ||
== Team 1 == | == Team 1 == | ||
| − | + | === Integrate SR proxy into service resolving interceptor === | |
| + | Show that service resolution takes place during start of a JAX-WS Service Consumer. | ||
| + | * Demo failing Consumer startup, caused by failed lookup, because service provider is missing in Service Registry. | ||
| + | * Demo successful start and show in log that lok-up was art of consumer start. | ||
| + | |||
| + | === Policy matching service resolver === | ||
| + | * Feature is [[Swordfish_Documentation:_Feature_Completenes_Definition | complete]]: Installation Feature is Separate Plugin/OSGi Bundle. Brief Documentation is available (see below), An example Policy assertion for the Swordfish flight booking example shall be provided. | ||
| + | * Demonstrate a Service Lookup, where out of 2 Services matching based on WSDL only one Service is matching based on the policy. Show the agreed policy. As we decided to have the policy integrated into the WSDL, the only difference between the 2 WSDL's shall be the policy. | ||
| + | * Demonstrate a failed Service Lookup because on non matching policies. Show the corresponding Error message. | ||
| + | * Integration Tests shall cover all possible parameter values of the policies. | ||
| + | * Documentation on the matching process and example policy assertions shall be provided in the Swordfish Documentation Wiki. | ||
| + | |||
| + | |||
| + | === JAX-WS Service integration with ODE === | ||
| + | === Service Registry: Admin Interface === | ||
== Team 2 == | == Team 2 == | ||
Revision as of 08:14, 11 March 2009
{{#eclipseproject:rt.swordfish}}
Contents
Sprint Goals
Duration: Mon 09.03- Thu 19.03
Team 1
- Integrate SR proxy into service resolving interceptor
- Policy matching service resolver
- JAX-WS Service integration with ODE
- Service Registry: Admin Interface
Team 2
- Installer: Update Site for runtime and tools
- Setup Swordfish target platform
- JAX-WS service: create/compile
- JAX-WS service: run bundle
- JAX-WS service: export JAX-WS bundle as JAR
Demo Scope
Team 1
Integrate SR proxy into service resolving interceptor
Show that service resolution takes place during start of a JAX-WS Service Consumer.
- Demo failing Consumer startup, caused by failed lookup, because service provider is missing in Service Registry.
- Demo successful start and show in log that lok-up was art of consumer start.
Policy matching service resolver
- Feature is complete: Installation Feature is Separate Plugin/OSGi Bundle. Brief Documentation is available (see below), An example Policy assertion for the Swordfish flight booking example shall be provided.
- Demonstrate a Service Lookup, where out of 2 Services matching based on WSDL only one Service is matching based on the policy. Show the agreed policy. As we decided to have the policy integrated into the WSDL, the only difference between the 2 WSDL's shall be the policy.
- Demonstrate a failed Service Lookup because on non matching policies. Show the corresponding Error message.
- Integration Tests shall cover all possible parameter values of the policies.
- Documentation on the matching process and example policy assertions shall be provided in the Swordfish Documentation Wiki.
JAX-WS Service integration with ODE
Service Registry: Admin Interface
Team 2
Installer: Update Site for runtime and tools
Demo how a service developer can install swordfish in his eclipse.
Setup Swordfish target platform
Demo how a service developer can set swordfish as a target platform for his plugins.
JAX-WS service: create/compile
Demo how a service developer can write a JAX-WS Service using Eclipse and compile it.
JAX-WS service: run bundle
Demo how a swordfish developer can run a CXF Swordfish Bundle in Eclipse:
- Show how JAX-WS Provider can be started.
- Show which parameters can be entered for a service call on consumer side.
- Run a Request-Response service call, demo how to see outgoing and received message.
JAX-WS service: export JAX-WS bundle as JAR
As a Swordfish Developer I would like to export my CXF Swordfish bundle as JAR file.
Feature Completeness
Demo that features are complete complete:
- Installation: The toolset required for the tasks above can be installed as Eclipse Plugin.
- Deployment: (to be discussed): Does the setting of the target platform also apply to the tool itself?
- Start/Run/Control: All execution steps of the user stories above can be run from Eclipse.
- Documentation: Documentation shall be provided for all user stories above in the Swordfish Wiki. Is Eclipsehelp feasible also?
- Examples: demo that the toolsa can be applied to the Swordfish flight booking example.
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