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 "STP Call for Scenarios"
| (7 intermediate revisions by 2 users not shown) | |||
| Line 11: | Line 11: | ||
| − | + | == Basic Getting Started Scenarios == | |
* [[Creating a really simple SOA Service & Testing it]] | * [[Creating a really simple SOA Service & Testing it]] | ||
| Line 17: | Line 17: | ||
* [[Adding an Additional Runtime]] | * [[Adding an Additional Runtime]] | ||
| − | * [[ | + | * [[Enable an existing Java Class as a SOA Service using Jax-ws]] |
| + | |||
| + | * [[Enterprise SOA Developer Scenario]] | ||
Latest revision as of 10:45, 31 May 2006
As part of an effort to direct our ongoing work, the STP project is calling for contribution of relevant scenarios. A scenario is different from a use-case in that it describes a flow of actions and events that lead to a goal. Our own goal here is to drive the STP milestones content by addressing scenarios that we receive.
Please feel free to post a named scenario linked from this page and include your email address so that
we can contact you to flesh out more details should the need arise. Discussion of scenarios will
take place on stp-dev. The STP team may perform minor editorial changes
to any scenarios for the purposes of clarification.