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.
Enable an existing Java Class as a SOA Service using Jax-ws
Revision as of 10:35, 23 May 2006 by Askehill.iona.com (Talk | contribs)
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 (POJO) as a Web Service
- Annotations will be used to create the Web Service
- A runtime which support Java Annotations has been pre-selected
- The interface on the object will need no modification and is granular enough to offer as a web service
Scenario Details
- The user will need to create a generic STP project to get started
- Once created, the java object (and any supporting classes) will need to be imported into the Eclipse environment and validated
- With valid Java, the user can proceed with annotating the class identifying which methods will need to be exposed as a Web Service. The tools will provide validation so that methods which cannot be exposed are correctly identified, and annotations are parsed to ensure they properly comply to JAX WS specifications
- When the annotations are complete any additional artefact's that are required by the SOA runtime are implemented and saved into the project (e.g. WSDL if required)
- The user can then deploy this service for test purposes and either use provided STP test tools or a third party application to test the service.