|
67 | 67 | have <link xlink:href="http://exist-db.org">eXist</link>
|
68 | 68 | running on your local system. By default eXist runs on
|
69 | 69 | port <code>8080</code> so that when you set your web
|
70 |
| - browser to <link |
71 |
| - xlink:href="http://localhost:8080/exist/" |
72 |
| - >http://localhost:8080/exist/</link> you should see |
| 70 | + browser to <link xlink:href="http://localhost:8080/exist/">http://localhost:8080/exist/</link> you should see |
73 | 71 | the eXist homepage come up.</para>
|
74 | 72 | <para>You can also run this tutorial on a remote eXist server. If you
|
75 | 73 | are doing this, you must replace the server name
|
|
120 | 118 | <emphasis role="bold">XRX</emphasis> is the name of the web
|
121 | 119 | application architecture that we are introducing in this guide.
|
122 | 120 | The term XRX comes from the combination of XForms, REST, and
|
123 |
| - XQuery. The term was <link |
124 |
| - xlink:href="http://archive.oreilly.com/pub/post/xrx_a_simple_elegant_disruptiv_1.html" |
125 |
| - >coined</link> by Dan McCreary. XForms are used in the |
| 121 | + XQuery. The term was <link xlink:href="http://archive.oreilly.com/pub/post/xrx_a_simple_elegant_disruptiv_1.html">coined</link> by Dan McCreary. XForms are used in the |
126 | 122 | client (web browser), REST is the interface between the client
|
127 | 123 | and the server, and XQuery is the server language. Two of the
|
128 | 124 | most significant advantages of XRX over other architectures are:
|
|
174 | 170 | SOAP interface testing tools are required. All you need to test
|
175 | 171 | your web services is a web browser. For example, the home page
|
176 | 172 | of the test application under the default configuration will be
|
177 |
| - <link |
178 |
| - xlink:href="http://localhost:8080/exist/apps/term/index.html" |
179 |
| - >http://localhost:8080/exist/apps/term/index.html</link>.</para> |
| 173 | + <link xlink:href="http://localhost:8080/exist/apps/term/index.html">http://localhost:8080/exist/apps/term/index.html</link>.</para> |
180 | 174 | <para>Several additional terms and concepts are helpful in understanding the XRX approach:</para>
|
181 | 175 | <para>
|
182 | 176 | <emphasis role="bold">WebDAV</emphasis> is a protocol for transferring files, and we use eXist's WebDAV interface to move files to and from
|
|
210 | 204 | <listitem>
|
211 | 205 | <para>
|
212 | 206 | <emphasis role="bold">Apps</emphasis>: XRX applications
|
213 |
| - should be stored within the <emphasis role="bold" |
214 |
| - >/db/apps</emphasis> parent collection. </para> |
| 207 | + should be stored within the <emphasis role="bold">/db/apps</emphasis> parent collection. </para> |
215 | 208 | </listitem>
|
216 | 209 | <listitem>
|
217 | 210 | <para>
|
|
277 | 270 | has created a specification for application metadata, called
|
278 | 271 | EXPath Packaging System. eXist supports and extends this
|
279 | 272 | module. This tutorial will not cover this file's structure,
|
280 |
| - but you can learn more about this by reading <link |
281 |
| - xlink:href="https://exist-db.org/exist/apps/doc/repo.xml" |
282 |
| - />. </para> |
| 273 | + but you can learn more about this by reading <link xlink:href="https://exist-db.org/exist/apps/doc/repo.xml"/>. </para> |
283 | 274 | </listitem>
|
284 | 275 | </orderedlist>
|
285 | 276 | <para>You are always free to change the names of the collection or the
|
|
446 | 437 | publish-status-code. (By using the repo.xml Deployment
|
447 | 438 | Descriptor's "prepare" field, you can automate the installation
|
448 | 439 | of this collection.xconf file into the target location; see
|
449 |
| - <link |
450 |
| - xlink:href="https://exist-db.org/exist/apps/doc/repo.xml#D1.4.10" |
451 |
| - />.)</para> |
| 440 | + <link xlink:href="https://exist-db.org/exist/apps/doc/repo.xml#D1.4.10"/>.)</para> |
452 | 441 | </sect2>
|
453 | 442 |
|
454 | 443 | <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
|
|
648 | 637 | The last control is the <tag>xf:select1</tag> control that
|
649 | 638 | allows the user to select one value from a list of values. (For
|
650 | 639 | a complete discussion of the XForms controls we suggest you use
|
651 |
| - the XForms Wikibook at <link |
652 |
| - xlink:href="http://en.wikibooks.org/wiki/XForms" |
653 |
| - >http://en.wikibooks.org/wiki/XForms</link>. The Input Form |
| 640 | + the XForms Wikibook at <link xlink:href="http://en.wikibooks.org/wiki/XForms">http://en.wikibooks.org/wiki/XForms</link>. The Input Form |
654 | 641 | Controls section goes through each of the controls in the XForms
|
655 | 642 | specification. In addition to the standard controls there are
|
656 | 643 | other controls that can also be integrated directly into XForms,
|
|
778 | 765 | reduce duplication and then reference these functions in
|
779 | 766 | each of your queries. For example, you could put the HTML
|
780 | 767 | boilerplate into a style module. You could also explore
|
781 |
| - eXist's HTML templating module; see <link |
782 |
| - xlink:href="https://exist-db.org/exist/apps/doc/templating.xml" |
783 |
| - />.</para> |
| 768 | + eXist's HTML templating module; see <link xlink:href="https://exist-db.org/exist/apps/doc/templating.xml"/>.</para> |
784 | 769 | </listitem>
|
785 | 770 | <listitem>
|
786 | 771 | <para>Change the <code>list-items.xq</code> to use HTML tables to view each item.</para>
|
|
832 | 817 | <listitem>
|
833 | 818 | <para>Modify the collection configuration file for the
|
834 | 819 | <code>/db/apps/terms/data</code> collection to enable
|
835 |
| - versioning when items are updated. See <link |
836 |
| - xlink:href="https://exist-db.org/exist/apps/doc/versioning.xml" |
837 |
| - />.</para> |
| 820 | + versioning when items are updated. See <link xlink:href="https://exist-db.org/exist/apps/doc/versioning.xml"/>.</para> |
838 | 821 | </listitem>
|
839 | 822 | </orderedlist>
|
840 | 823 | </sect1>
|
|
0 commit comments