No, it can actually run JSP (Java Server Pages) in the server 8.1.7 release.
It's nice for active content on Intranets. I have no number for scaling on
Internet sites, but I'd assume if you were below 1,000,000 hits a day you'd
be ok with it running on a small sparc.
Thor HW
----- Original Message -----
From: "David Gallardo" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, August 24, 2000 3:35 PM
Subject: Re: Oracle JDeveloper experiences
> JSP in this context is a Java Stored Procedure. Sometimes SQL isn't
enough
> & you want to be able to do procedural stuff. Traditionally folks use
> proprietary languages for stored procedures in the database, such PL/SQL.
> Oracle introduced the ability to write stored procedures in Java in 8.1.5.
>
> Java stored procedures are slower than the native PL/SQL, but not too
much.
> Either lets us do data intensive procedures on the server which can be
> tremendously faster than processing on the client when this involves
pushing
> a lot of data back and forth over the wire.
>
> The advantages of using Java for stored procedures are that the code is
not
> in a proprietary language & that we can re-deploy it in another layer of
our
> architecture with little change--in an app server, for example.
>
> - David
>
> -----Original Message-----
> From: James Cook [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, August 24, 2000 5:15 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Oracle JDeveloper experiences
>
>
> I'm not aware of how Oracle runs a servlet/jsp from within it's database,
> but
> you are stating that it runs in the *database* and not their app server?
If
> so,
> are you guys gaining any advantages from this unusual structure?
>
> jim
>
>
> ----- Original Message -----
> From: "David Gallardo" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Thursday, August 24, 2000 4:48 PM
> Subject: Re: Oracle JDeveloper experiences
>
>
> > The ability to run and debug jsps deployed inside Oracle.
> >
> > As far as I know, (which admittedly is not much), you can't do this with
a
> > standard ide. So our development cycle is code & debug outside the
> > database, change the driver & deploy it inside the database (Oracle
> > loadjava), publish it as a procedure (i.e. map it to pl/sql interface) &
> > hope it works the same as it did before.
> >
> >
> > -----Original Message-----
> > From: James Cook [mailto:[EMAIL PROTECTED]]
> > Sent: Thursday, August 24, 2000 4:18 PM
> > To: [EMAIL PROTECTED]
> > Subject: Re: Oracle JDeveloper experiences
> >
> >
> > I don't have an opinion on JDeveloper, but I do have a question.
> >
> > JDeveloper has evolved from code that Oracle licensed from Inprise,
namely
> > JBuilder. I don't believe that JDeveloper has sprung from the latest
(past
> > year
> > or so) all-Java technology that Inprise has switched to. Specifically, I
> > understand that JDeveloper is a slightly customized version of JBuilder
> 3.0
> > (a
> > windows-only technology). I don't consider a Windows-only development
tool
> > to be
> > a problem, so I don't have any biases in that direction.
> >
> > My question is, what has Oracle added to the product to make it more
> > attractive
> > than Inprise JBuilder. I have many memories of JBuilder 3.0 being very
> > unstable
> > due to its hybrid native/Java implementation. The latest versions are
> > pure-Java
> > and infinitely more enjoyable to use. (I ack that there are some who
> prefer
> > the
> > speed of the native version, but I'll take the stability.)
> >
> > Just curious what Oracle has added to the product to make it even worth
> > considering?
> >
> > jim
> >
> >
> >
> > ----- Original Message -----
> > From: "David Gallardo" <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Thursday, August 24, 2000 2:36 PM
> > Subject: Re: Oracle JDeveloper experiences
> >
> >
> > > We are evaluating JDeveloper for developing JSPs. We are using Oracle
> > 8.1.5
> > > and we can view JSP's source code, but can't debug. It seems that we
> will
> > > need to upgrade to 8.1.6 in order to do this, but it does look like
it's
> > > possible. Specifically, the failure is because JDeveloper is looking
for
> > > procedures in the DBMS_JAVA package that are not present in the 8.1.5
> > > version.
> > >
> > > -----Original Message-----
> > > From: Sachin Mallapurkar [mailto:[EMAIL PROTECTED]]
> > > Sent: Thursday, August 24, 2000 1:03 PM
> > > To: [EMAIL PROTECTED]
> > > Subject: Oracle JDeveloper experiences
> > >
> > >
> > > Hello,
> > >
> > > Could anyone please share their experiences with the Oracle JDeveloper
> > > product?
> > >
> > > >From what I have read, it seems that version 3.1 of Oracle JDeveloper
> > > allows visual development for JSPs and EJBs. My project will involve
> > > development with JSPs and EJBs.
> > >
> > > Thanks in advance.
> > >
> > > Sachin
> > >
> > >
> >
>
===========================================================================
> > > 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".
>
>
===========================================================================
> 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".
