/[classpath]/classpath/org/omg/CORBA/package.html
ViewVC logotype

Diff of /classpath/org/omg/CORBA/package.html

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 1.5 by mark, Sat Jul 2 20:32:58 2005 UTC revision 1.6 by audriusa, Tue Aug 9 11:37:51 2005 UTC
# Line 40  exception statement from your version. - Line 40  exception statement from your version. -
40  <head><title>GNU Classpath - org.omg.CORBA</title></head>  <head><title>GNU Classpath - org.omg.CORBA</title></head>
41    
42  <body>  <body>
43  This package provides the support of <a href="www.omg.org">OMG</a>  This package provides the support of <a href="http://www.CORBA.org">CORBA</a>;
44  <a href="www.CORBA.org">CORBA</a>; see <a href="#overview">overview</a>  see <a href="#overview">overview</a> of the implemented functionality.
45  of the implemented functionality. CORBA is an open, vendor independent  CORBA a system that applications use to work over networks. CORBA messages
46  system that applications use to work together over networks.  Thie purpose  are binary, not text oriented. They practically cary no "data wrapping"
47  of this package is to provide CORBA APIs to java programming language,  information like XML &lt;opening&gt; &lt;/closing&gt; tags. Hence CORBA
48  including the fully functional Object Request Broker ({@link org.omg.CORBA.ORB}).  objects much easier exchange large amounts of binary data. CORBA can work
49    in such data-intensive application areas as telecommunications or radio
50    broadcasting.
51  <a name="overview">  <a name="overview">
52  <h4>Overview of the currently implemented CORBA functionality</h4>  <h4>Overview of the currently implemented CORBA functionality</h4>
53  <p>The CORBA implementation in the Classpath project is now a working prototype.  The CORBA implementation in the Classpath project is now a working
54   This prototype is interoperable with Sun's implementation v 1.4, transferring  prototype.
55   object references, primitive types, narrow and wide strings, arrays, structures  <ul>
56   and trees between these two platforms. The thrown exceptions are also transferred  <li>This prototype is interoperable with Sun's implementation v 1.4,
57   and handled. The support for stringified object references (IORs) is implemented.  transferring object references, primitive types, narrow and wide strings,
58   The redirection commands works, LOCATION_FORWARD_PERM changing the target address  arrays, structures  and trees between these two platforms.
59   until the application is restarted and LOCATION_FORWARD redirecting for the  </li>
60   current session only. Both Little and Big Endian encoded messages  <li>The prototype provides interoperable support for the Abstract interface
61   are accepted. The encoding of the sent messages is the same as used in the   and Value types. Those appear in 1.3, being a feature of CORBA 2.3.
62   stringified IOR reference of that object or Big Endian, if no such data  </li>
63   available.  <li>The remote exceptions are also transferred and handled as expected.
64   </p>  </li>
65    <p>  <li>The support for parsing stringified object references (IORs), both
66   The current release supports the Value types that appeared since v 1.3 and are  Big and Little Endian encoded, is implemented.
67   something between CORBA structures (no methods, data local) and CORBA objects  </li>
68   (both methods and data remote). Value type has local data, can have  <li>The redirection commands works, LOCATION_FORWARD_PERM changing the
69   local methods and is transferred by value, not by IOR reference.  target address until the application is restarted and LOCATION_FORWARD
70   </p>  redirecting for the current session only.
71   <p>  </li>
72   You can use both request-oriented (based on {@link org.omg.CORBA.Request})  <li>Both Little and Big Endian encoded messages are accepted. The encoding
73   and stream-oriented (based on {@link org.omg.CORBA.portable.ObjectImpl})  of the sent messages is the same as used in the stringified IOR reference
74   invocation models. The current release includes the working examples, demonstrating  of that object or Big Endian, if no such data available.
75   the client-server communication using both methods. These examples also show,  </li>
76   how to use the Classpath naming service. The IDL compiler is not yet written,  <li>You can use both request-oriented (based on {@link org.omg.CORBA.Request}
77   but as a side effect of the required compatibility, the implementation seems  and stream-oriented (based on {@link org.omg.CORBA.portable.ObjectImpl}
78   accepting the output of the Sun's 1.3 idlj.</p>  invocation models. The current release includes the working examples,
79    demonstrating the client-server communication using both methods.
80    </li>
81    <li>These examples also show,  how to use the Classpath naming service.
82    </li>
83    <li>The IDL compiler is not yet written (and not even started), but as a
84     side effect of the required compatibility, the implementation seems
85    accepting the output of the Sun's idlj.
86    </li>
87    <li>The Portable Object Adapter is already released. For details on POA,
88    see the {@link org.omg.PortableServer} package.</li>
89    <li>We provide the implementation of the {@link org.omg.DynamicAny}
90    package. ORB returns the working DynAnyFactory that produces working
91    DynAny's as defined in OMG specification.</li>
92    <li>All GNU Classpath classes in omg.org namespace are newly written using
93     the OMG .pdf document (Version 3.0.3, formal/04-03-12).
94    </li>
95    </ul>
96    
97   @author Audrius Meskauskas, Lithuania (AudriusA@Bioinformatics.org)   @author Audrius Meskauskas, Lithuania (AudriusA@Bioinformatics.org)
98  </body>  </body>

Legend:
Removed from v.1.5  
changed lines
  Added in v.1.6

savannah-hackers-public@gnu.org
ViewVC Help
Powered by ViewVC 1.1.26