Notation conventions, General syntax notation – HP Integrity NonStop H-Series User Manual
Page 17
This appendix contains the
ei_setenv
script.
Appendix I: Hibernate Environment Setup Script
This appendix describes the steps required to install
Hibernate Annotations Libraries on your NonStop system.
Appendix J: Installing Hibernate Annotations Libraries
on NonStop
This appendix describes the steps required to install
Hibernate EntityManager Libraries on your NonStop
system.
Appendix K: Installing Hibernate EntityManager Libraries
on NonStop
Part V helps you to use the Spring Transaction Manager
and integrate Spring with Hibernate, Axis2/Java, and
MyFaces.
Part V: Integrating Frameworks
This chapter helps you to use the Spring Transaction
Manager.
Chapter 18: Using Spring Transaction Manager
This chapter helps you to integrate Hibernate into the
Spring framework.
Chapter 19: Integrating Hibernate into Spring
This chapter helps you to integrate JPA with Hibernate
into the Spring framework.
Chapter 20: Integrating JPA with Hibernate into Spring
This chapter helps you to integrate Axis2/Java into the
Spring framework.
Chapter 21: Integrating Axis2/Java into Spring
This chapter helps you to integrate MyFaces into the
Spring framework.
Chapter 22: Integrating MyFaces into Spring
This chapter provides answers to some frequently asked
questions.
Chapter 23: Frequently Asked Questions
Notation Conventions
General Syntax Notation
This list summarizes the notation conventions for syntax presentation in this manual.
UPPERCASE LETTERS
Uppercase letters indicate keywords and reserved words. Type these items exactly as shown.
Items not enclosed in brackets are required. For example:
MAXATTACH
Italic Letters
Italic letters, regardless of font, indicate variable items that you supply. Items not enclosed
in brackets are required. For example:
file-name
Computer Type
Computer type letters indicate:
•
C and Open System Services (OSS) keywords, commands, and reserved words. Type
these items exactly as shown. Items not enclosed in brackets are required. For example:
Use the
cextdecs.h
header file.
•
Text displayed by the computer. For example:
Last Logon: 14 May 2006, 08:02:23
•
A listing of computer code. For example
if (listen(sock, 1) < 0)
{
perror("Listen Error");
exit(-1);
}
Notation Conventions
17