If you make those classes available in the classpath, of course you can. The restriction means which optional packages are available BY DEFAULT on each environment. As long as an applet has access to some RMI flavor (the same than the server) it can accomplish the connection. Tha requires for the applet programmer to make some .jar file (usually provided by the server vendor) available in the classpath.
I'm also posting this to EJB-INTEREST HTH, Juan Pablo Lorandi Chief Software Architect Code Foundry Ltd. [EMAIL PROTECTED] Barberstown, Straffan, Co. Kildare, Ireland. Tel: +353-1-6012050 Fax: +353-1-6012051 Mobile: +353-86-2157900 www.codefoundry.com > -----Original Message----- > From: Johan Eltes [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, April 16, 2002 8:39 PM > To: Juan Pablo Lorandi > Subject: RE: Software Architecture > > > Juan, > > My conclusion is that I cannot use EJB home- and remote > interfaces from the applet container, since they depend on > the EJB client api (inheriting EJBHome/EJBObject). If that is > not a valid conclusion, what else would the restriction > stated in the table mean to the applet programmer? > > /Johan > > -----Original Message----- > From: Juan Pablo Lorandi [mailto:[EMAIL PROTECTED]] > Sent: den 16 april 2002 13:00 > To: 'Johan Eltes' > Subject: RE: Software Architecture > > Wow... When did the specs change THAT much? > > If an applet can use the correct RMI flavor to communicate > with an EJB server, it could be done > > The first choice is what I usually prefer. > The choice should be made taking into account a lot of > details that Sebastien does not provide. > > Juan Pablo Lorandi > Chief Software Architect > Code Foundry Ltd. > [EMAIL PROTECTED] > > Barberstown, Straffan, Co. Kildare, Ireland. > Tel: +353-1-6012050 Fax: +353-1-6012051 > Mobile: +353-86-2157900 > www.codefoundry.com > > > > -----Original Message----- > > From: A mailing list for Enterprise JavaBeans development > > [mailto:[EMAIL PROTECTED]] On Behalf Of Johan Eltes > > Sent: Tuesday, April 16, 2002 9:33 AM > > To: [EMAIL PROTECTED] > > Subject: Re: Software Architecture > > > > > > Your second solution is not spec complient, unless you use CORBA to > > communicate with the EJB. This leaves you with only one > option. Your > > problem solved :-) > > > > /Johan > > > > citerar BOUTTE Sebastien <[EMAIL PROTECTED]>: > > > > > Hi, > > > > > > I have a simple problem in software design ; i would like to know > > what is > > > the best between these two solutions ? > > > For Communication between applet and EJB: > > > > > > Applet ------ Servlet (Connectivity servlet) ----- EJB > > > (In this, the proxy servlet is just redirecting the request to the > > EJB) > > > > > > or > > > > > > Applet ------ EJB > > > (In this, the applet is communicating with the ejb via his stub) > > > > > > What are the advantages/disadvantages of those solutions ? > > > > > > Thanks > > > > > > Boutt� S�bastien > > > > > > ������������������������� > > > To unsubscribe, send email to [EMAIL PROTECTED] and include in > > the body > > > of the message "signoff EJB-INTEREST". For general help, > send email > > to > > > [EMAIL PROTECTED] and include in the body of the > message "help". > > > > > > > > > > ============================================================== > > ============= > > To unsubscribe, send email to [EMAIL PROTECTED] and > include in the > > body of the message "signoff EJB-INTEREST". For general help, send > > email to [EMAIL PROTECTED] and include in the body of > the message > > "help". > > > ==========================================================================To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
