| <html> |
| <head> |
| <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"> |
| <title>3.3.2. Deploying the fragment</title> |
| <link rel="stylesheet" type="text/css" href="../../css/style.css"> |
| <meta name="generator" content="DocBook XSL Stylesheets V1.78.1"> |
| <link rel="home" href="../index.html" title="Jubula Developer Manual"> |
| <link rel="up" href="remoteControlExtension.html" title="3.3. Remote control extension"> |
| <link rel="prev" href="creating-the-fragment.html" title="3.3.1. Creating the fragment"> |
| <link rel="next" href="extensionExamples.html" title="3.4. ITE and remote control extension examples"> |
| </head> |
| <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"> |
| <div class="navheader"> |
| <table width="100%" summary="Navigation header"> |
| <tr><th colspan="3" align="center">3.3.2. Deploying the fragment</th></tr> |
| <tr> |
| <td width="20%" align="left"> |
| <a accesskey="p" href="creating-the-fragment.html">Prev</a> </td> |
| <th width="60%" align="center">3.3. Remote control extension</th> |
| <td width="20%" align="right"> <a accesskey="n" href="extensionExamples.html">Next</a> |
| </td> |
| </tr> |
| </table> |
| <hr> |
| </div> |
| <div xmlns:d="http://docbook.org/ns/docbook" class="breadcrumbs"> |
| <span class="breadcrumb-link"><a href="../index.html">Jubula Developer Manual</a></span> > <span class="breadcrumb-link"><a href="toolkitExtension.html">Creating toolkit extensions for custom UI widgets</a></span> > <span class="breadcrumb-link"><a href="remoteControlExtension.html">Remote control extension</a></span> > <span class="breadcrumb-node">Deploying the fragment</span> |
| </div> |
| <div class="section"> |
| <div class="titlepage"><div><div><h3 class="title"> |
| <a name="deploying-the-fragment"></a>3.3.2. Deploying the fragment</h3></div></div></div> |
| <p> |
| Once you have written your fragment, you still need to make all |
| components aware of its presence. This is done by exporting the |
| fragment and deploying it into the remote control. |
| </p> |
| <p> |
| There are different ways for installing your fragment into the |
| remote control, depending on the AUT Agent used and the specific |
| AUT. You are free to use either the embedded AUT Agent or the |
| standalone AUT Agent. Also your AUT can be based upon the OSGi |
| framework or not. The following table shows an overview, where |
| to deploy your fragment: |
| </p> |
| <div class="informaltable"><table border="1"> |
| <colgroup> |
| <col align="center"> |
| <col align="center"> |
| <col align="center"> |
| </colgroup> |
| <tbody> |
| <tr> |
| <td align="center"> |
| |
| </td> |
| <td align="center"> |
| without OSGi<br xmlns:d="http://docbook.org/ns/docbook">(Swing, SWT, JavaFX) |
| </td> |
| <td align="center"> |
| with OSGi<br xmlns:d="http://docbook.org/ns/docbook">(RCP, GEF) |
| </td> |
| </tr> |
| <tr> |
| <td align="center"> |
| embedded<br xmlns:d="http://docbook.org/ns/docbook">AUT Agent |
| </td> |
| <td align="center"> |
| ITE |
| </td> |
| <td rowspan="2" align="center"> |
| AUT |
| </td> |
| </tr> |
| <tr> |
| <td align="center"> |
| standalone<br xmlns:d="http://docbook.org/ns/docbook">AUT agent |
| </td> |
| <td align="center"> |
| standalone<br xmlns:d="http://docbook.org/ns/docbook">AUT agent |
| </td> |
| </tr> |
| </tbody> |
| </table></div> |
| <p> |
| It shows, in which case you usually deploy your fragment into |
| </p> |
| <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> |
| <li class="listitem"><p> |
| the ITE with a feature including your fragment, |
| </p></li> |
| <li class="listitem"><p> |
| the standalone AUT Agent by adding your fragment to its |
| configuration, or |
| </p></li> |
| <li class="listitem"><p> |
| the AUT with a feature including your fragment. |
| </p></li> |
| </ul></div> |
| <p> |
| The configuration of the standalone AUT Agent can be done by modifying the file |
| <span class="input">server/configuration/config.ini</span>. |
| There you have to append <span class="input">,fragment_id</span> at the end of the line starting with |
| <span class="input">osgi.bundles=</span>. Make sure that the bundles are comma-separated. It is also necessary |
| to add the argument <span class="input">-clean</span> in the file <span class="input">server/autagent.ini</span>, |
| when deploying a new version with the same fragment ID. Apart from the deploying methods mentioned, it is also possible to install |
| your fragment using a p2 repository or the OSGi console. |
| </p> |
| <p xmlns:d="http://docbook.org/ns/docbook"><table> |
| <colgroup> |
| <col> |
| <col> |
| </colgroup> |
| <tbody><tr> |
| <td><img align="bottom" width="100" height="91" src="../images/img2.jpg"></td> |
| <td class="topbotline"><span class="strong"><strong>If you have deployed fragments for the JavaFX RC |
| bundle, you have to keep in mind that if you are executing the ITE |
| with Java 7 the RC bundle is not active and therefore the wiring for |
| the fragments has not been done by the OSGI framework. The current |
| workaround in Jubula is that all the fragments for the JavaFX RC |
| bundle are added, without taking any version ranges from the fragments |
| into account. |
| </strong></span></td> |
| </tr></tbody> |
| </table></p> |
| <p> |
| You should be able to test your new component once you have |
| installed the toolkit feature into the ITE and the fragment as |
| described below. |
| </p> |
| </div> |
| <br xmlns:d="http://docbook.org/ns/docbook"><hr xmlns:d="http://docbook.org/ns/docbook"> |
| <address xmlns:d="http://docbook.org/ns/docbook">Copyright BREDEX GmbH 2015. Made available under the Eclipse Public License v1.0.</address> |
| <br xmlns:d="http://docbook.org/ns/docbook"> |
| </body> |
| </html> |
