Hi all,
I have a stand-alone, Swing application that I need to extend to a two-tier system, so there will be multiple instances of the Swing application and a central server. My job is to make changes to the Swing application and implement the server application from the ground up.
What is the best practice for Swing applications to interact with a server? I don't want to go with RMI since not only is it becoming obsolete but also there is no guarantee that the applications and the server will be on the same network.
Should I implement the server with EJB3 or Spring? What protocol should be used?
Thanks!
-
Swing and server interaction (1 messages)
- Posted by: John Doe
- Posted on: July 27 2010 22:20 EDT
Threaded Messages (1)
- RE :Swing and server interaction by Vaibhav Nirkhe on August 05 2010 09:47 EDT
-
RE :Swing and server interaction[ Go to top ]
- Posted by: Vaibhav Nirkhe
- Posted on: August 05 2010 09:47 EDT
- in response to John Doe
Hi Brian,
If your server implementation does'nt require any aop support then EJB3 is a handy option to choose.EJB3 will provide all the container services also with RMI support and this all can be implemented in EJB3 with less complexity since it uses annotations and minimal xml configuration.
Best Regards !!