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 "Enable an existing Java Class as a SOA Service using Jax-ws"
(→Overview) |
|||
| Line 4: | Line 4: | ||
== Assumptions == | == Assumptions == | ||
| − | As this can be quite a large scenario, we'll need to narrow down this down with some very restrictive assumptions. | + | As this can be quite a large scenario, we'll need to narrow down this down with some very restrictive assumptions. |
| + | * User wishes to expose Java Object as Web Service | ||
== Scenario Details == | == Scenario Details == | ||
Revision as of 09:37, 23 May 2006
Overview
In this instance, a user is coming to the STP tooling for assistance in taking an already existing application and enabling it so that it can participate as a SOA Service.
Assumptions
As this can be quite a large scenario, we'll need to narrow down this down with some very restrictive assumptions.
- User wishes to expose Java Object as Web Service