• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

custom service running sockets

 
Ranch Hand
Posts: 34
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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
 
reply
    Bookmark Topic Watch Topic
  • New Topic