| <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> |
| <html> |
| <head> |
| <meta HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=iso-8859-1"> |
| <title>Java in UNO and OpenOffice</title> |
| <meta NAME="KEYWORDS" CONTENT="sandbox"> |
| </head> |
| <body LINK="#444488" VLINK="#444488" bgcolor="#eeeeff"><A NAME="__Top__"></A> |
| |
| <table WIDTH=100% BORDER=0 CELLPADDING=4 CELLSPACING=0> |
| <col WIDTH=75> |
| <tr> |
| <td bgcolor="#666699"> |
| <h1 ALIGN=CENTER STYLE="margin-top: 0cm; text-decoration: none"> |
| <font COLOR="#ffffff" SIZE=6>Java in UNO and OpenOffice</font> |
| </h1> |
| </td> |
| </tr> |
| </table> |
| |
| <P> |
| |
| |
| Java is the famous and easy to learn computer language |
| developed by sun. Because OpenOffice is based on the |
| language independent component model <a href="../../common/man/uno.html">UNO</a>, components |
| can be written in any language for which exists a so |
| called language binding. Fortunately there is such a |
| language binding for java. |
| |
| <P> |
| |
| It follows a short list of what is important for the java developer, |
| who wants to write components for UNO or OpenOffice: |
| |
| |
| <ul> |
| <li> How are UNO types <a href="map_idl_to_java.html">mapped</a> to java?</li> |
| <li> What is the <a href="jurt.html">base functionlity</a> to use UNO from Java?</li> |
| <li>How to write a <a href="java_component_howto.html">java component</a>?</li> |
| <li> <a href="jurt.html#BaseServices">Which java components do exist?</a> |
| <li> Which other components do exist (<a href="http://www.openoffice.org/source/browse/udk/stoc/source/">stoc/source</a>, |
| io/source)? |
| <li> What does the <a href="http://api.openoffice.org">api</a> looks like?</li> |
| <li> How to <a href="register_java_components.html">integrate</a> a java component |
| into the office?</li> |
| <li> How to write <a href="UnoApp.html">UNO java applications?</a></li> |
| <li> How to access OO or sun ONE webtop from <a href="AccessingOfficeFromRemote.html">remote</a>?</li> |
| <li>How to find javadoc-generated <a href="../ref/overview-tree.html">documentation</a>?</li> |
| </ul> |
| |
| <p> |
| |
| |
| People who have made the first steps may want to know |
| how all this is possible and how and in which projects |
| the connection between UNO and java is implemented, so please |
| have a look at the following table, which gives an overview |
| of the involved projects: |
| |
| <p> |
| |
| |
| |
| |
| <table CELLPADDING="4" CELLSPACING="1" bgcolor="#ffffff" WIDTH="100%"> |
| <tr> |
| <td COLSPAN="2" bgcolor="#00315A" ALIGN="CENTER"> |
| <FONT COLOR="#FFFFFF" FACE="Arial, Helvetica" SIZE="2">Modules involved with java UNO</font> |
| </td> |
| </tr> |
| |
| <tr> |
| <th bgcolor="#99CCFF" ALIGN="CENTER"><font COLOR="#00315A" FACE="Arial, Helvetica" SIZE="2">Module</font></th> |
| <th bgcolor="#99CCFF" ALIGN="CENTER"><font COLOR="#00315A" FACE="Arial, Helvetica" SIZE="2">Function</font></th> |
| </tr> |
| |
| <tr> |
| <td bgcolor="#f0f0f0" VALIGN="top"><code><A HREF="../../common/man/tools.html#javamaker">codemaker/javamaker</A></code></td> |
| <td bgcolor="#f0f0f0" VALIGN="top">the tool, which generates java interface descriptions out of the type library</td> |
| </tr> |
| |
| <tr> |
| |
| <td bgcolor="#f0f0f0" VALIGN="top"><code><a href="../ref/com/sun/star/tools/uno/package-tree.html">jut</a> |
| - Java Uno Tools</code></td> |
| |
| <td bgcolor="#f0f0f0" VALIGN="top">tools for java uno components (<a href="register_java_components.html">RegComp</a> |
| / <a href="UnoApp.html">UnoApp</a> / <a href="../ref/com/sun/star/tools/uno/DumpType.html">DumpType</a>)</td> |
| </tr> |
| |
| <tr> |
| |
| <td bgcolor="#f0f0f0" VALIGN="top"><code><a href="../ref/com/sun/star/comp/helper/package-tree.html">juh</a> |
| - Java Uno Helper</code></td> |
| <td bgcolor="#f0f0f0" VALIGN="top">allowes the boostrapping of a servicemanager and gives access to the native component loader</td> |
| </tr> |
| |
| <tr> |
| <td bgcolor="#f0f0f0" VALIGN="top"><code><a href="jurt.html">jurt</a> - Java Uno RunTime</code></td> |
| <td bgcolor="#f0f0f0" VALIGN="top">the core of java UNO</td> |
| </tr> |
| |
| <tr> |
| <td bgcolor="#f0f0f0" VALIGN="top"><code><a href="sandbox.html"> sandbox</a></code></td> |
| <td bgcolor="#f0f0f0" VALIGN="top">an execution environment for remote loadable classes</td> |
| </tr> |
| |
| <tr> |
| |
| <td bgcolor="#f0f0f0" VALIGN="top"><code><a href="ridl.html">ridl</a> - Java |
| Runtime Interface Definition Library</code></td> |
| |
| <td bgcolor="#f0f0f0" VALIGN="top">the <a href="typelibrary.html">typelibrary</a> |
| and the precompiled java interfaces of the <a href="http://api.openoffice.org/source/browse/api/udkapi/">udkapi</a></td> |
| </tr> |
| |
| <tr> |
| <td bgcolor="#f0f0f0" VALIGN="top"><code>bridges/source/java_uno</code></td> |
| <td bgcolor="#f0f0f0" VALIGN="top">the <a href="java_uno_bridge.html">native java uno bridge</a>, so the java components can be accessed from binary UNO</td> |
| </tr> |
| |
| <tr> |
| <td bgcolor="#f0f0f0" VALIGN="top"><code>stoc/source/javaloader</code></td> |
| <td bgcolor="#f0f0f0" VALIGN="top">the <a href="javaloader.html">java component loader</a> to load java components</td> |
| </tr> |
| |
| |
| <tr> |
| <td bgcolor="#f0f0f0" VALIGN="top"><code>stoc/source/javavm</code></td> |
| <td bgcolor="#f0f0f0" VALIGN="top">the <a href="javavm.html">java vm service</a>, which gives access to a native java vm</td> |
| </tr> |
| |
| <tr> |
| |
| <td bgcolor="#f0f0f0" VALIGN="top"><code><a href="http://api.openoffice.org/source/browse/api/unoil/">unoil</a> |
| - UNO interface library</code></td> |
| <td bgcolor="#f0f0f0" VALIGN="top">the precompiled java interfaces of the <a href="http://api.openoffice.org">OO api</a></td> |
| </tr> |
| |
| </table |
| |
| |
| > |
| <p> Further interesting is how the mapping of objects between UNO and JAVA and |
| vice versa works. Especially the <a href="lifecycle.html">lifecycle</a> may |
| be of interest. Also we have a little <a href=faq.html>FAQ</a> about java UNO. |
| This <a href=conventions.html>convention document</a> gives some hints to find |
| your way through the source. |
| </body> |
| </html> |
