The right approach would be to create a JCA adapter for that. JCA adapter can be used for outbound or inbound connectivity. You're allowed to start thread or schedule work in a JCA adpater. The inbound connectivity from the JCA adapter to the EJB is done using custom message-driven bean.
- The adapter start a socket listener and manage the connection from remote clients
- When a packet is received, a message is delivered to a custom MDB
- The MDB can then delegate the processing to other EJBs
You can even start transaction from the JCA connector so that the delivery of the message/packet to the EJB is transacted. JCA is part of the Java EE specifications and is supported by all application servers.
Another approach (but not compliant with the spec), is to start the thread that listens to the socket from a ServletContextListener
. The thread will run in the web layer and you can call the EJB as usual. Dependency injection will not work, but JNDI lookup should still be ok.
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…