42 |
<body> |
<body> |
43 |
This package provides the support of <a href="http://www.CORBA.org">CORBA</a>; |
This package provides the support of <a href="http://www.CORBA.org">CORBA</a>; |
44 |
see <a href="#overview">overview</a> of the implemented functionality. |
see <a href="#overview">overview</a> of the implemented functionality. |
45 |
|
<p> |
46 |
CORBA a system that applications use to work over networks. CORBA messages |
CORBA a system that applications use to work over networks. CORBA messages |
47 |
are binary, not text oriented. They practically cary no "data wrapping" |
are binary, not text oriented. They practically cary no "data wrapping" |
48 |
information like XML <opening> </closing> tags. Hence CORBA |
information like XML <opening> </closing> tags. Hence CORBA |
49 |
objects much easier exchange large amounts of binary data. CORBA can work |
objects easier exchange large amounts of binary data. CORBA can work |
50 |
in such data-intensive application areas as telecommunications or radio |
in such data-intensive application areas as telecommunications or radio |
51 |
broadcasting. |
broadcasting. Java programs connect to CORBA objects without care |
52 |
|
about what platform they run on, where they exist in the network, or what |
53 |
|
language they were written in. The remote CORBA objects appear to the |
54 |
|
programmer as the ordinary Java objects and can be passed as |
55 |
|
parameters in both remote or local method invocations. |
56 |
|
</p><p> |
57 |
|
The CORBA processing unit is divided into {@link org.omg.CORBA.Object} |
58 |
|
that is exposed to the client and the servant |
59 |
|
({@link org.omg.PortableServer.Servant} where the method, invoked on |
60 |
|
object, is finally delegated. It can be multiple objects per servant or |
61 |
|
multiple servants per object. The servant for particular object or |
62 |
|
even particular call can be dynamically chosen at run time using |
63 |
|
{@link org.omg.PortableServer.ServantManager}. |
64 |
|
</p><p> |
65 |
|
All stages of both local and remote invocations on CORBA objects can be |
66 |
|
monitored and modified using {@link org.omg.PortableInterceptor.Interceptor}. |
67 |
|
The interceptors can add an extra data to the CORBA message (these data |
68 |
|
can be later accessed by other interceptor on remote side). |
69 |
|
</p> |
70 |
<a name="overview"> |
<a name="overview"> |
71 |
<h4>Overview of the currently implemented CORBA functionality</h4> |
<h4>Overview of the currently implemented CORBA functionality</h4> |
72 |
The CORBA implementation in the Classpath project is now a working |
The CORBA implementation in the Classpath project is now a working |
108 |
<li>We provide the implementation of the {@link org.omg.DynamicAny} |
<li>We provide the implementation of the {@link org.omg.DynamicAny} |
109 |
package. ORB returns the working DynAnyFactory that produces working |
package. ORB returns the working DynAnyFactory that produces working |
110 |
DynAny's as defined in OMG specification.</li> |
DynAny's as defined in OMG specification.</li> |
111 |
|
<li>The Portable Interceptor is also complete. See |
112 |
|
{@link org.omg.PortableInterceptor} package for details how to register |
113 |
|
and use CORBA interceptors. |
114 |
<li>All GNU Classpath classes in omg.org namespace are newly written using |
<li>All GNU Classpath classes in omg.org namespace are newly written using |
115 |
the OMG .pdf document (Version 3.0.3, formal/04-03-12). |
the OMG .pdf document (Version 3.0.3, formal/04-03-12). |
116 |
</li> |
</li> |