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: JAX-WS Code Generation"
(→Use Cases) |
m (→Use Cases) |
||
| Line 15: | Line 15: | ||
= Use Cases = | = Use Cases = | ||
See User Stories for WSDL first code generation: | See User Stories for WSDL first code generation: | ||
| − | [[Swordfish_Documentation:_User_Stories:_Service_Developer#S090 | Consumer]] | + | *[[Swordfish_Documentation:_User_Stories:_Service_Developer#S090 | Consumer]] |
| − | [[Swordfish_Documentation:_User_Stories:_Service_Developer#S095 | Provider]] | + | *[[Swordfish_Documentation:_User_Stories:_Service_Developer#S095 | Provider]] |
= Conditions of satisfaction = | = Conditions of satisfaction = | ||
Latest revision as of 05:47, 28 April 2009
{{#eclipseproject:rt.swordfish}}
In progress
Provide Feedback to this Feature on th Talk Page.
Contents
Description
Swordfish Code Generation based on JAX-WS specification
Current Problem / Pain
Currently JAX-WS participants for Swordfish need to be developed manually from scratch.
Advantages/Business Case
A Code Generation should enable the user to generate Skeleton and Proxy from WSDL.
Use Cases
See User Stories for WSDL first code generation:
Conditions of satisfaction
TBD
Limitations
TBD
Dependencies
Non functional aspects
Volume / Load aspects
Security aspects
Ease of Use
Architecture Outline/ Implementation Ideas
Open Questions
Return to Eclipse Swordfish Swordfish Product Backlog