|
Hibernate example source code file (Conventions.xml)
This example Hibernate source code file (Conventions.xml) is included in the DevDaily.com
"Java Source Code
Warehouse" project. The intent of this project is to help you "Learn Java by Example" TM.
The Hibernate Conventions.xml source code
<?xml version='1.0' encoding='utf-8' ?>
<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
]>
<section>
<title>Document Conventions
<para>
This manual uses several conventions to highlight certain words and phrases and draw attention to specific pieces of information.
</para>
<para>
In PDF and paper editions, this manual uses typefaces drawn from the <ulink url="https://fedorahosted.org/liberation-fonts/">Liberation Fonts set. The Liberation Fonts set is also used in HTML editions if the set is installed on your system. If not, alternative but equivalent typefaces are displayed. Note: Red Hat Enterprise Linux 5 and later includes the Liberation Fonts set by default.
</para>
<section>
<title>Typographic Conventions
<para>
Four typographic conventions are used to call attention to specific words and phrases. These conventions, and the circumstances they apply to, are as follows.
</para>
<para>
<literal>Mono-spaced Bold
</para>
<para>
Used to highlight system input, including shell commands, file names and paths. Also used to highlight keycaps and key combinations. For example:
</para>
<blockquote>
<para>
To see the contents of the file <filename>my_next_bestselling_novel in your current working directory, enter the cat my_next_bestselling_novel command at the shell prompt and press Enter to execute the command.
</para>
</blockquote>
<para>
The above includes a file name, a shell command and a keycap, all presented in mono-spaced bold and all distinguishable thanks to context.
</para>
<para>
Key combinations can be distinguished from keycaps by the hyphen connecting each part of a key combination. For example:
</para>
<blockquote>
<para>
Press <keycap>Enter to execute the command.
</para>
<para>
Press <keycombo>CtrlAltF1 to switch to the first virtual terminal. Press CtrlAltF7 to return to your X-Windows session.
</para>
</blockquote>
<para>
The first paragraph highlights the particular keycap to press. The second highlights two key combinations (each a set of three keycaps with each set pressed simultaneously).
</para>
<para>
If source code is discussed, class names, methods, functions, variable names and returned values mentioned within a paragraph will be presented as above, in <literal>mono-spaced bold. For example:
</para>
<blockquote>
<para>
File-related classes include <classname>filesystem for file systems, file for files, and dir for directories. Each class has its own associated set of permissions.
</para>
</blockquote>
<para>
<application>Proportional Bold
</para>
<para>
This denotes words or phrases encountered on a system, including application names; dialog box text; labeled buttons; check-box and radio button labels; menu titles and sub-menu titles. For example:
</para>
<blockquote>
<para>
Choose <menuchoice>SystemPreferencesMouse from the main menu bar to launch Mouse Preferences. In the Buttons tab, click the Left-handed mouse check box and click Close to switch the primary mouse button from the left to the right (making the mouse suitable for use in the left hand).
</para>
<para>
To insert a special character into a <application>gedit file, choose ApplicationsAccessoriesCharacter Map from the main menu bar. Next, choose SearchFind… from the Character Map menu bar, type the name of the character in the Search field and click Next. The character you sought will be highlighted in the Character Table. Double-click this highlighted character to place it in the Text to copy field and then click the Copy button. Now switch back to your document and choose EditPaste from the gedit menu bar.
</para>
</blockquote>
<para>
The above text includes application names; system-wide menu names and items; application-specific menu names; and buttons and text found within a GUI interface, all presented in proportional bold and all distinguishable by context.
</para>
<para>
<command>Mono-spaced Bold Italic or Proportional Bold Italic
</para>
<para>
Whether mono-spaced bold or proportional bold, the addition of italics indicates replaceable or variable text. Italics denotes text you do not input literally or displayed text that changes depending on circumstance. For example:
</para>
<blockquote>
<para>
To connect to a remote machine using ssh, type <command>ssh username@domain.name at a shell prompt. If the remote machine is example.com and your username on that machine is john, type ssh john@example.com.
</para>
<para>
The <command>mount -o remount file-system command remounts the named file system. For example, to remount the /home file system, the command is mount -o remount /home.
</para>
<para>
To see the version of a currently installed package, use the <command>rpm -q package command. It will return a result as follows: package-version-release.
</para>
</blockquote>
<para>
Note the words in bold italics above — username, domain.name, file-system, package, version and release. Each word is a placeholder, either for text you enter when issuing a command or for text displayed by the system.
</para>
<para>
Aside from standard usage for presenting the title of a work, italics denotes the first use of a new and important term. For example:
</para>
<blockquote>
<para>
Publican is a <firstterm>DocBook publishing system.
</para>
</blockquote>
</section>
<section>
<title>Pull-quote Conventions
<para>
Terminal output and source code listings are set off visually from the surrounding text.
</para>
<para>
Output sent to a terminal is set in <computeroutput>mono-spaced roman and presented thus:
</para>
<screen>books Desktop documentation drafts mss photos stuff svn
books_tests Desktop1 downloads images notes scripts svgs
</screen>
<para>
Source-code listings are also set in <computeroutput>mono-spaced roman but add syntax highlighting as follows:
</para>
<programlisting language="Java">package org.jboss.book.jca.ex1;
import javax.naming.InitialContext;
public class ExClient
{
public static void main(String args[])
throws Exception
{
InitialContext iniCtx = new InitialContext();
Object ref = iniCtx.lookup("EchoBean");
EchoHome home = (EchoHome) ref;
Echo echo = home.create();
System.out.println("Created Echo");
System.out.println("Echo.echo('Hello') = " + echo.echo("Hello"));
}
}
</programlisting>
</section>
<section>
<title>Notes and Warnings
<para>
Finally, we use three visual styles to draw attention to information that might otherwise be overlooked.
</para>
<note>
<title>Note
<para>
Notes are tips, shortcuts or alternative approaches to the task at hand. Ignoring a note should have no negative consequences, but you might miss out on a trick that makes your life easier.
</para>
</note>
<important>
<title>Important
<para>
Important boxes detail things that are easily missed: configuration changes that only apply to the current session, or services that need restarting before an update will apply. Ignoring a box labeled 'Important' won't cause data loss but may cause irritation and frustration.
</para>
</important>
<warning>
<title>Warning
<para>
Warnings should not be ignored. Ignoring warnings will most likely cause data loss.
</para>
</warning>
</section>
</section>
Other Hibernate examples (source code examples)
Here is a short list of links related to this Hibernate Conventions.xml source code file:
|