Applet Communication

[scohan]

We have a swing front end that we want to convert to applets so we can run in a browser. Does it make sense to use EJBs within applets? Should we call servlets instead? With the latter, we'll have to convert from HttpServletResponse to jave objects in the applet won't we. Isn't that kind of kludgy? For the former, we run into firewall issues and having to plugin j2ee code to the browser, don't we?

We could use web services, but they wouldn't perform as well as the first two options, correct?

Thanks.

 

[toolkit]

I wouldn't like to advise either way. But there are quite a few links regarding this:

http://www.google.co.uk/search?q=using+EJBs+in+applets&ie=UTF-8&hl=en&meta=

Some techniques to consider.

1. Use EJBs.
2. Use sockets.
3. Use an 'HTTP-Tunnel'

We use the 3rd technique. That is, the applet talks to a servlet that passes back serialised objects down the tunnel.

 

[sedj]

It depends entirely on what kind of application/transaction you are doing ... all options have their pros/cons depending on what you wish to achieve.
You are however (IMO) incorrect about *web services* - I would say they would be quicker than EJB emebedded in applets. And a heck of a lot easier than mincing around with Applets, signing them, tunnelling through the firewall etc etc.

Is this for an internet or intranet application ?