Internet Servers Division
Zhou Ye firstname.lastname@example.org
Ankur Sharma email@example.com
Java - CORBA binding
Providing Internet access to CORBA based systems brings the power of
scalable, open, CORBA based systems to the World Wide Web. Oracle WebServer 2.0
provides three interpreters for application development and execution :
as well as an Oracle Web Request Broker API for custom extensions and
cartridges. Web client access to external systems can be provided either at
the WRB*API level by developing a Web Server cartridge, or through the Java
Interpreter. The Oracle WebServer Java Interpreter currently provides seamless
access to PL/SQL procedures stored and executed in the Oracle database by
modeling PL/SQL packages as Java classes. We are also working on a Java-CORBA
language binding and runtime implementation to provide internet access to
CORBA based distributed systems from the WebServer.
- PL/SQL - providing seamless access to data and procedures stored in the
Oracle Universal Server.
- LiveHTML - enabling easy to write server side applications and scripts, and
- Java - providing a full Java based development and runtime
Providing internet access to CORBA systems from Java requires two components :
- A Java language mapping for CORBA IDL.
- A standard Java stub interface to facilitate interoperability and a open
standards based environment.
The Java language mapping
We are developing a Java-CORBA IDL language mapping to provide representation
all CORBA datatypes and constructs in the Java language. We provide mappings
all basic and constructed datatypes, including any and unions, but excluding
integers. We also provide a mapping for modules, interfaces, operations and
and support multiple inheritance. The language mapping is completely
independant of any
specific ORB, yet is flexible enough to allow different ORB's to support it
and allows for ORB specific implementation enhancements.
The Java-CORBA stub mapping
We are also working on an ORB implementation independant Java stub mapping of
the CORBA IDL language mapping. To fully enable mobile distributed code and
applications based on standards, we believe that a standard stub interface
needs to be
defined that models an ORB as a set of fundamental and uniform Java classes.
facilitates portable application development and enables Java applets to run
on browsers that may natively support different ORB implementations.
In the absence of a standard stub mapping, portable and ORB independant
is not possible. A Java applet may potentially be downloaded by any browser
running on any platform, but if the specific ORB implementation is not
available on that particular browser and the Java stub generated is tied to a
specific ORB, it may not be possible to run the downloaded applet. Given the
high mobility of web content and applications, we feel that a standard Java
stub mapping is an important component of a system providing access to web
clients. We have designed such a java stub mapping and our Java lanuage
mapping mentioned above also takes this into account.
Enabling a standard Java language mapping and a Java stub mapping will also
interoperability and application portability throughout the web. Compilers and
other tools provided by various vendors can also be used interchangeably
regardless of the specific ORB.