WS and TCP endpoints in the same SI app

[ealden]

Currently, we have an SI 2.0.1 app with a couple of TCP endpoints. It simply receives requests from a TCP inbound channel adapter, processes it, hands off to another system using a TCP outbound channel adapter, waits for a reply, and returns it back to the original sender. The entire app is started as a console application whose main() starts up the ApplicationContext.

We plan to add a couple of WS endpoints to provide senders with another way to send requests. Based on the reference the easiest way is to put the entire thing inside a servlet container. Is it advisable to do this with our current setup?

I'm thinking that either we do the one above or we start our own servlet container inside Spring and somehow use that to expose the WS endpoint. Would appreciate insights on this.

Thank you and happy new year

[Gary Russell]

Yes, the easiest thing to do is put the entire app in a web container; you should have no difficulties using TCP endpoints therein.