Project: talendesb
Issue TESB-2401: Improve support for data services with several operations in the Talend runtime
WSDL first data services may consist of several operations, each one represented by a job. Even normally for web services the unit of deployment is the service currently in TESB the job / operation ist the unit deployment. Consequences - Configuration data such as endpoints, features that apply to the service are attached to the job. First job installed wins. - No way to ensure the data service in the runtime really represents the service described in the WSDL. - WSDL exposed by the service in the runtime does not correspond to the one specified in tooling - Very hackish implementation Solution idea - Provide an explicit service / wsdl item in tooling, a first class citizen like job and route. Properties such a endpoint, enabled features, map which job is implementing which operation are stored in this item - User can generate bundle based on the service item which includes all this information - Job controller in runtime is able to handle this new kind of bundle (start service expose wsdl, forward request to correct job based on map, ....) Activities: - Synchronize with Tooling about new service / wsdl item, how the generated artifact looks like - improve the job controller to handle new kind of bundle - ... Open questions - how to handle job first services Out of scope: - Improvements regarding the documentation - only basic testing, full roundtrip test with tooling is a separate feature.
Story points: 8