Oracle database desupport so many JAVA technologies in the coming version? I
don't believe it. Why Oracle has such decision? It makes me feel that using
JAVA in Oracle is not so "secure", suddenly all features will be desupported
in the next version and need to use another Oracle product!!! My God...
"Cristian Veronesi" <veronesic_at_libero.it> wrote in message
news:3CC3F97A.7030409_at_libero.it...
> Vladimir M. Zakharychev wrote:
>
> > Don't think it's going to be phased out now that it's there and so much
effort
> > was put into making it work. As of J2EE - correct me if I am wrong, but
I
> > think it *is* supported, at least at version 1.2. Not sure when and if
it will
> > be updated to support 1.3 or 1.4...
>
> Quoted from Metalink:
>
>
> "With the introduction in Oracle9iAS release 1.0.2.2 of a new,
> lighter-weight,
> easier to use, faster and certified
> J2EE container (a.k.a. OC4J), Oracle will desupport the Java 2
> Enterprise Edition (J2EE) and CORBA stacks from the database,
> post Oracle9iDB Release 1 (9.0.1); however the database-embedded Java VM
> (a.k.a.
> Oracle JVM) will still be available and provide Java 2 Standard
> Edition (J2SE) features to support Java Stored Procedures, JDBC and SQLJ
> in the database.
> Starting from Oracle9iDB R2 (9.2.0), the following technologies will no
> longer be supported in the database:
> Enterprise Java Beans (EJB),
> Common Object Request Broker Architecture (CORBA),
> Oracle Java Server Pages (OJSP)
> Oracle Servlet Engine (OSE)
> The 9.0.1 release will be the last database release to support this
> stack but customers are encouraged to migrate
> existing J2EE based applications running in the database to OC4J, the
> new J2EE container in Oracle9iAS, now."
>
> Kind Regards, Cristian
>
Received on Mon Apr 22 2002 - 08:29:48 CDT
