Contents

Why need to build the wtp server bridge

One suggestion from the lastest stp meeting (Apr24,25, dublin): Since wtp server framework is quite popular now, it will be nice if we can deploy component directly to wtp server within SOAS.

Thus we build this bridge to connect between those two frameworks. It will allow developer to use wtp server as connection profile defined in stp. Thus we can deploy service to wtp server without modify current code base, which is all based on connection profile.

How it works

Changes

StpProfileManager

Instead of using ProfileManager from DTP, we delegate all profile related calls to the new StpProfileManager.
It will first lookup profile form DTP, then retrieve profile from wtp server delegate. The result will be combination of both.

WtpServerBridge

It used to retrive related wtp server from ServerCore according to server type <-> connection profile ID mappings defined in the bridge extension point.

IWTPServerAdater

Adapter interface to convert server instance to connection profile class. For each server type supported by this bridge, there
will be an server adapter.