In porting our
Tomcat application over to Websphere, I found a custom service to be what we are looking for, EXCEPT it appears it doesn't allow the use of sockets. Our application running in Tomcat starts/stops when Tomcat does. Its purpose is to connect via a socket to a server. All
servlets queue up messages that are then sent over this socket. We are limited to this architecture because of the legacy server we are talking via sockets to.
In looking at Websphere, it appears a custom service is exactly what we need, except I read it doesn't allow the use of sockets. Is there some way around this? Is there another way to create a global object within WS that I can then use a socket connection with?
thx