Java in Stored Procs

Today one of my developers asked about having java code in our DB (10.2.0.2). He had already been playing around with it some, and found it much slower. Not really a scientific test, but he found that calling java routines from the PowerBuilder front-end could handle 1 million records in 52s, where as calling the same routine from within his stored proc was much slower (10k records in 24s). He's now looking at native compilation [1] as a way to speed things up.

We are "a java shop" and the main goal here is re-use of existing data processing code, so that we don't have to update the same logic in multiple places.

I thought I remembered reading a paper or presentation that mentioned some solid reasons for keeping java out of the database. Feuerstein or Kyte perhaps.

I'd like to know what you fine folks have to say about the matter. Should never the twain meet? Anyone with ncomp experience?

[1] http://download.oracle.com/docs/cd/B19306_01/java.102/b14187/chten.htm#sthref505

-- 
Don Seiler
oracle blog: http://ora.seiler.us
ultimate: http://www.mufc.us
--
http://www.freelists.org/webpage/oracle-l