-
1. Re: Java EE7 replacement for multi-threaded socket server
jameslivingston Feb 8, 2016 5:17 PM (in response to sharkbite)What protocol will the socket be for? There is nothing in EE for handling arbitrary sockets, in general the container handles the protocol parts and various specs deal with the interface that applications interact with (e.g. Servlets for HTTP and related protocols like AJP).
-
2. Re: Java EE7 replacement for multi-threaded socket server
sharkbite Feb 9, 2016 12:18 AM (in response to jameslivingston)Hi James
Thank you for your expertise answer.
The socket is for TCP/IP
What about using JCA?
Thanks,
Daslan
-
3. Re: Java EE7 replacement for multi-threaded socket server
jameslivingston Feb 9, 2016 12:31 AM (in response to sharkbite)So an arbitrary network protocol then.
You could write a resource adapter which opens the socket, and use JCA inflow to deliver things to message driven beans. If you want arbitrary two way communication over the socket, I'm not sure how well that would work.
-
4. Re: Java EE7 replacement for multi-threaded socket server
sharkbite Feb 10, 2016 2:31 AM (in response to jameslivingston)Hi James
Thanks for the point in the write direction. I will need synchronous communication. Is there a way to to use synchronous MDB's in Wildly 8.1.0/Java EE7 I remember seeing this some where is the Java EE5 spec,
Also where can I find information about spawning threads in Wildly 8.1.0/Java EE7?
What about MBeans? I have seen this mentioned in early versions of JBoss.
Do you think I should use them for this implementation?
Thanks,
Daslan