Actually, Java is not so bad idea. Aurora does pretty much the same thing
as PL/SQL and it is very hard to get to OS or network because security
doesn't let
you. On the plus side, bad programs in Java are more portable then the ones
in 
PL/SQL. IDE software for Java is better suited for duhvelopers then 
the one for PL/SQL.
You will have to increase Java pool and you will have to increase system 
tablespace because your developers will start  abusing loadjava almost 
instantly and start loading .jar files (like for XML, for instance). Also, 
your CPU and RAM usage will go up fairly quickly so  you might consider 
convincing your boss to finally do that HW upgrade.
Expect attempts to use thin JDBC driver. The nice features of the thin
driver 
are 
a) It's written entirely in Java, which makes it much slower then an
   optimized C code like OCI driver and, therefore, preferred by duhvelopers
   in the name of "generality" and "universality". Stupidity is another
   very universal thing.
b) The thin driver can only use dedicated server connection which does
miracles
   for load balancing. There is "connection pooling", which also requires
   dedicated server to work. Because it cannot use MTS and TNS in general,
   thin driver must have a hard-wired connection string written in the code
or 
   parameter file, which apparently doesn't diminish "generality" and 
   "universality".

> -----Original Message-----
> From: Rachel Carmichael [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, September 05, 2002 9:08 AM
> To: Multiple recipients of list ORACLE-L
> Subject: java stored procedures
> 
> 
> This really is my week for asking for help.
> 
> We have a project lead/developer here who wants to use a java stored
> procedure, wrapped in a PL/SQL function, to implement a 
> search function
> on the site.
> 
> Besides the fact that this is the first I've heard of the request, and
> that I think he is reinventing the wheel in what he wants to 
> do in this
> procedure (normalize text data that we already GET normalized
> elsewhere), and that we are supposed to go into QA testing by the end
> of the month and he STILL hasn't locked down the schema etc....
> 
> Personal prejudices aside, I've heard vague rumblings that Java in the
> database is not optimal. We'll be in 9iR2, although he's developing
> against an 8.1.7 database (don't ask, I'm not responsible for that
> database other than to provide him with schema ddl, there IS no real
> development server here).
> 
> Before I categorically say no or yes, are there any "gotchas" 
> I need to
> look out for?
> 
> Thanks
> 
> Rachel
> 
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Finance - Get real-time stock quotes
> http://finance.yahoo.com
> -- 
> Please see the official ORACLE-L FAQ: http://www.orafaq.com
> -- 
> Author: Rachel Carmichael
>   INET: [EMAIL PROTECTED]
> 
> Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
> San Diego, California        -- Public Internet access / Mailing Lists
> --------------------------------------------------------------------
> To REMOVE yourself from this mailing list, send an E-Mail message
> to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
> the message BODY, include a line containing: UNSUB ORACLE-L
> (or the name of mailing list you want to be removed from).  You may
> also send the HELP command for other information (like subscribing).
> 
-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- 
Author: Gogala, Mladen
  INET: [EMAIL PROTECTED]

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).

Reply via email to