![]() ![]() ![]() ![]() ![]() ![]() |
You can implement Enterprise JavaBeans that use RMI-IIOP to provide EJB interoperability in heterogeneous server environments:
A Java RMI client can use an ORB and IIOP to access Enterprise beans residing on a WebLogic Server instance. See Understanding Enterprise JavaBeans in Programming WebLogic Enterprise JavaBeans.
A non-Java platform CORBA/IDL client can access any Enterprise bean object on WebLogic Server. The sources of the mapping information are the EJB classes as defined in the Java source files. WebLogic Server provides the weblogic.appc
utility for generating required IDL files. These files represent the CORBA view into the state and behavior of the target EJB. Use the weblogic.appc
utility to:
The weblogic.appc
utility supports a number of command qualifiers. See Developing a CORBA/IDL Client.
Resulting files are processed using the compiler, reading source files from the idlSources
directory and generating CORBA C++ stub and skeleton files. These generated files are sufficient for all CORBA data types with the exception of value types (see
Limitations of WebLogic RMI-IIOP in Programming WebLogic RMI ). Generated IDL files are placed in the idlSources
directory. The Java-to-IDL process is full of pitfalls. Refer to the
Java Language Mapping to OMG IDL specification.
Also, Sun has an excellent guide, Enterprise JavaBeansTM Components and CORBA Clients: A Developer Guide.
The following is an example of how to generate the IDL from a bean you have already created:
> java weblogic.appc -compiler javac -keepgenerated
-idl -idlDirectory idlSources
build\std_ejb_iiop.jar
%APPLICATIONS%\ejb_iiop.jar
> javac -d %CLIENT_CLASSES% Trader.java TraderHome.java
TradeResult.java Client.java
>%IDL2CPP% idlSources\examples\rmi_iiop\ejb\Trader.idl
. . .
>%IDL2CPP% idlSources\javax\ejb\RemoveException.idl
![]() ![]() ![]() |