Hi!
Indigo Blue wrote:
> I know that this is not recommended but the only reason for that I came
> accross was compatibility of browser VMs and security restrictions on
> applets.
That's not it (mainly). If you look in J2EE and the EJB spec you won't
see applets mentioned that often, but the reason is not that applets are
inherently *bad* clients, it's just that EJB and J2EE doesn't *mandate*
that they are supported, since it is not mandatory to have neither a
global JNDI namespace (only java:comp/env is mandatory!!), nor is it
*required* to have a distribution protocol. Given these two
non-mandatory features, which are vital for applets, applets aren't
talked about that much.
> But theoretically if I have the beans on the same host from which the applet
> comes and I have my users use Java Plug-in (I know that Mac still remains a
> problem but let's leave that aside for the sake of this argument) I don't
> see the downside of the applet as a client of my EJBs. Has anyone done it
> yet?
> I would appreciate some perspectives and clarifications regarding this
> issue.
I cannot see any problems with doing the above.
/Rickard
--
Rickard �berg
@home: +46 13 177937
Email: [EMAIL PROTECTED]
http://www.telkel.com
http://www.jboss.org
http://www.dreambean.com
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
