When I say "Oracle's ORB", I mean the correct version of Visigenic's that we
ship with 8.i - version 3.2. We use the Visigenic ORB in 8.i, not something of
our making. I don't think our rmi/iiop will work in version 3.4 - we had to
make slight changes for version 3.4.
> You do need to use Oracle's ORB when doing EJB's. The old Netscape ORB won't
> work, and we're using our own version of RMI/IIOP (the JDK 1.2 rmi/iiop
> standard wasn't available when I did this).
>
> ----- Original Message -----
> From: John Collins <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Saturday, October 09, 1999 8:33 AM
> Subject: Re: AW: The truth about EJB's
>
>
> Actually, if the problem is with the browser's internal ORB (Netscape, I
> assume), then it isn't the sandbox problem but an ORB compatibility problem.
> Netscape includes a rather old version of VisiBroker. Using the 1.2 plug-in
> should solve the problem, or you can explicitly load a different ORB along
> with your applet. You shouldn't need to use Oracle's ORB. The latter
> approach may make applet download times unacceptable, of course. Note that
> most ORBs do not yet support the CallByValue mechanism needed by RMI/IIOP. I
> believe the latest version of VisiBroker does.
>
> Good luck.
>
> John Collins
>
> Hermann Schmitt wrote:
>
> > Hallo,
> > I think the cause are the so called "sandbox restrictions" for applets. If
> > you use the Java Plug-in 1.2 with the browsers, you can use JDK 1.2., which
> > does not haave the samd box restrictions.
> > Hermann Schmitt
> >
> > -----Urspr|ngliche Nachricht-----
> > Von: A mailing list for Enterprise JavaBeans development
> > [mailto:[EMAIL PROTECTED]]Im Auftrag von scott coleman
> > Gesendet: Freitag, 8. Oktober 1999 10:21
> > An: [EMAIL PROTECTED]
> > Betreff: The truth about EJB's
> > Wichtigkeit: Hoch
> >
> > Hi
> >
> > I wrote to one of your collegues and they informed to forward my letter
> > to you, so here it is, it
> >
> > The problem is that we have a server with an Oracle database that the
> > EJB's are deployed into. We then try to activate an EJB through a web
> > browser and it is impossible. But if we have the same code but activate
> > it through the applet veiwer or a Application it works. This appears to
> > be due to the fact that the Web Browser has its own internal ORB. And
> > oracle need there own to use the EJB's deployed into their database.
> > They have informed me that this is probably the case for all EJB
> > vendors.
> > I thought of using PowerTier as our EJB vendor, but their web pages
> > implies that ther have the same problem. The only way to instantiate and
> > use an EJB on the server from with an Client Web Browser is to use
> > servlets, for creation and method calls etc.
> > Also i looked at the sun web page at a section called Communication
> > Protocols and it states "Browsers can invoke the application through a
> > servlet running on the HTTP server. The browser communicates with the
> > servlet using HTTP, and the servlet communicates with the application
> > using RMI" which to me implies that you can only invoke an EJB on the
> > server and communicate with it using a servlet running on the HTTP
> > server.
> >
> > I hope this has defined my question, is it possible to invoke and
> > communicate with an EJB on the Server directly from within a Web Browser
> > without using servlets.
> >
> > I look forward to your reply
> > Scott
> > [EMAIL PROTECTED]
> >
> > ===========================================================================
> > 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".
>
> ===========================================================================
> 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".
