notid/gitea-docker
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

app store.

Browse Source
This commit is contained in:
Bryce Covert
2016-05-25 10:21:27 -07:00
parent 96938aafd3
commit f56779259b
577 changed files with 25518 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

662
desktop/test-osx/Tick's Tales.app/Contents/MacOS/jre/man/man1/java.1 Normal file
View File

@@ -0,0 +1,662 @@
." Copyright (c) 1994, 2013, Oracle and/or its affiliates. All rights reserved.
."
.TH java 1 "18 Jul 2013"
.LP
.SH "Name"
java \- the Java application launcher
.LP
.SH "SYNOPSIS"
.LP
.nf
\f3
.fl
\fP\f3java\fP [ \f2options\fP ] \f2class\fP [ \f2argument ...\fP ]
.fl
\f3java\fP [ \f2options\fP ] \f3\-jar\fP \f2file.jar\fP [ \f2argument ...\fP ]
.fl
.fi
.LP
.RS 3
.TP 3
options
Command\-line options. See \f2Options\fP.
.TP 3
class
The name of the class to be called.
.TP 3
file.jar
The name of the JAR file to be called. Used only with the \f3\-jar\fP command.
.TP 3
argument
The arguments passed to the \f3main\fP function.
.RE
.LP
.SH "DESCRIPTION"
.LP
.LP
The \f3java\fP command starts a Java application. It does this by starting a Java runtime environment, loading a specified class, and calling that class's \f3main\fP method.
.LP
.LP
The method must be declared public and static, it must not return any value, and it must accept a String array as a parameter. The method declaration has the following form:
.LP
.nf
\f3
.fl
public static void main(String args[])
.fl
\fP
.fi
.LP
.LP
By default, the first argument without an option is the name of the class to be called. A fully qualified class name should be used. If the \f3\-jar\fP option is specified, then the first non\-option argument is the name of a JAR file containing class and resource files for the application, with the startup class indicated by the Main\-Class manifest header.
.LP
.LP
The Java runtime searches for the startup class, and other classes used, in three sets of locations: the bootstrap class path, the installed extensions, and the user class path.
.LP
.LP
Non\-option arguments after the class name or JAR file name are passed to the \f3main\fP function.
.LP
.SH "OPTIONS"
.LP
.LP
The launcher has a set of standard options that are supported in the current runtime environment.
.LP
.LP
In addition, the current implementations of the virtual machines support a set of nonstandard options that are subject to change in future releases. See \f2Nonstandard Options\fP.
.LP
.SS
Standard Options
.LP
.RS 3
.TP 3
\-client
Selects the Java HotSpot Client VM. A 64\-bit capable JDK currently ignores this option and instead uses the Java Hotspot Server VM.
.br
.br
For default Java VM selection, see \f2Server\-Class Machine Detection\fP at http://docs.oracle.com/javase/7/docs/technotes/guides/vm/server\-class.html
.TP 3
\-server
Selects the Java HotSpot Server VM. On a 64\-bit capable JDK, only the Java Hotspot Server VM is supported so the \f3\-\fP\f3server\fP option is implicit.
.br
.br
For default a Java VM selection, see \f2Server\-Class Machine Detection\fP at http://docs.oracle.com/javase/7/docs/technotes/guides/vm/server\-class.html
.TP 3
\-agentlib:libname[=options]
Loads native agent library \f2libname\fP, for example:
.nf
\f3
.fl
\-agentlib:hprof
.fl
.fl
\-agentlib:jdwp=help
.fl
.fl
\-agentlib:hprof=help
.fl
\fP
.fi
See \f2JVMTI Agent Command\-Line Options\fP at http://docs.oracle.com/javase/7/docs/platform/jvmti/jvmti.html#starting/dd>
.TP 3
\-agentpath:pathname[=options]
Loads a native agent library by full \f2pathname\fP. See \f2JVMTI Command\-Line Options\fP at http://docs.oracle.com/javase/7/docs/platform/jvmti/jvmti.html#starting
.TP 3
\-classpath classpath, \-cp classpath
Specifies a list of directories, JAR files, and ZIP archives to search for class files. Separate class path entries with colons (:). Specifying \f3\-classpath\fP or \f3\-cp\fP overrides any setting of the \f2CLASSPATH\fP environment variable.
.br
.br
If \f3\-classpath\fP and \f3\-cp\fP are not used and \f2CLASSPATH\fP is not set, then the user class path consists of the current directory (.).
.br
.br
As a special convenience, a class path element that contains a base name of \f3*\fP is considered equivalent to specifying a list of all the files in the directory with the extension .jar or .JAR. A Java program cannot tell the difference between the two invocations.
.br
.br
For example, if directory mydir contains a.jar and b.JAR, then the class path element \f3mydir/*\fP is expanded to a A.jar:b.JAR, except that the order of jar files is unspecified. All jar files in the specified directory, even hidden ones, are included in the list. A class path entry consisting simply of \f3*\fP expands to a list of all the jar files in the current directory. The \f2CLASSPATH\fP environment variable, where defined, will be similarly expanded. Any class path wildcard expansion occurs before the Java VM is started. No Java program will ever see wild cards that are not expanded except by querying the environment. For example, by calling \f3System.getenv("CLASSPATH")\fP.
.TP 3
\-Dproperty=value
Sets a system property value.
.TP 3
\-d32
Run the application in a 32\-bit environment. If a 32\-bit environment is not installed or is not supported, an error will be reported. By default, the application is run in a 32\-bit environment unless a 64\-bit only system is used.
.TP 3
\-d64
Run the application in a 64\-bit environment. If a 64\-bit environment is not installed or is not supported, an error will be reported. By default, the application is run in a 32\-bit environment unless a 64\-bit only system is used.
.br
.br
Currently only the Java HotSpot Server VM supports 64\-bit operation, and the \f3\-server\fP option is implicit with the use of \f3\-d64\fP. The \f3\-client\fP option is ignored with the use of \f3\-d64\fP. This is subject to change in a future release.
.TP 3
\-disableassertions[:package name"..." | :class name ], \-da[:package name"..." | :class name ]
Disable assertions. This is the default.
.br
.br
With no arguments, \f3\-disableassertions\fP or \f3\-da\fP disables assertions. With one argument ending in \f3"..."\fP, the switch disables assertions in the specified package and any subpackages. If the argument is \f3"..."\fP, then the switch disables assertions in the unnamed package in the current working directory. With one argument not ending in \f3"..."\fP, the switch disables assertions in the specified class.
.br
.br
To run a program with assertions enabled in \f3package com.wombat.fruitbat\fP but disabled in class \f3com.wombat.fruitbat.Brickbat\fP, the following command could be used:
.nf
\f3
.fl
java \-ea:com.wombat.fruitbat... \-da:com.wombat.fruitbat.Brickbat <Main Class>
.fl
\fP
.fi
The \f3\-disableassertions\fP and \f3\-da\fP switches apply to all class loaders and to system classes (which do not have a class loader). There is one exception to this rule: in their no\-argument form, the switches do not apply to system. This makes it easy to turn on asserts in all classes except for system classes. The \f3\-disablesystemassertions\fP option provides a separate swith to enable assertions in all system classes.
.TP 3
\-enableassertions[:package name"..." | :class name ], \-ea[:package name"..." | :class name ]
Enable assertions. Assertions are disabled by default.
.br
.br
With no arguments, \f3\-enableassertions\fP or \f3\-ea\fP enables assertions. With one argument ending in \f3"..."\fP, the switch enables assertions in the specified package and any subpackages. If the argument is \f3"..."\fP, then the switch enables assertions in the unnamed package in the current working directory. With one argument not ending in \f3"..."\fP, the switch enables assertions in the specified class.
.br
.br
If a single command contains multiple instances of these switches, then they are processed in order before loading any classes. So, for example, to run a program with assertions enabled only in package com.wombat.fruitbat (and any subpackages), the following command could be used:
.nf
\f3
.fl
java \-ea:com.wombat.fruitbat... <Main Class>
.fl
\fP
.fi
The \f3\-enableassertions\fP and \f3\-ea\fP switches apply to all class loaders and to system classes (which do not have a class loader). There is one exception to this rule: in their no\-argument form, the switches do not apply to system. This makes it easy to turn on asserts in all classes except for system classes. The \f3\-enablesystemassertions\fP option provides a separate switch to enable assertions in all system classes.
.TP 3
\-enablesystemassertions, \-esa
Enable assertions in all system classes (sets the default assertion status for system classes to true).
.TP 3
\-disablesystemassertions, \-dsa
Disables assertions in all system classes.
.TP 3
\-help or \-?
Displays usage information and exit.
.TP 3
\-jar
Executes a program encapsulated in a JAR file. The first argument is the name of a JAR file instead of a startup class name. For this option to work, the manifest of the JAR file must contain a line in the form \f3Main\-Class\fP: \f2classname\fP. Here, \f2classname\fP identifies the class with the \f3public static void main(String[] args)\fP method that serves as your application's starting point.
.br
.br
When you use this option, the JAR file is the source of all user classes, and other user class path settings are ignored.
.br
.br
JAR files that can be run with the \f3java \-jar\fP option can have their execute permissions set so they can be run without using \f3java \-jar\fP. See \f2JAR File Overview\fP at http://docs.oracle.com/javase/7/docs/technotes/guides/jar/jarGuide.html
.TP 3
\-javaagent:jarpath[=options]
Loads a Java programming language agent. For more information about instrumenting Java applications, see the java.lang.instrument package description in the Java API documentation at
.br
.na
\f2http://docs.oracle.com/javase/7/docs/api/java/lang/instrument/package\-summary.html\fP @
.fi
http://docs.oracle.com/javase/7/docs/api/java/lang/instrument/package\-summary.html
.TP 3
\-jre\-restrict\-search
Includes user\-private JREs in the version search.
.TP 3
\-no\-jre\-restrict\-search
Excludes user\-private JREs in the version search.
.TP 3
\-showversion
Displays version information and continues.
.TP 3
\-splash:imagepath
Shows splash screen with image specified by \f2imagepath\fP.
.TP 3
\-verbose, \-verbose:class
Displays information about each class loaded.
.TP 3
\-verbose:gc
Reports on each garbage collection event.
.TP 3
\-verbose:jni
Reports information about use of native methods and other Java Native Interface activity.
.TP 3
\-version
Displays version information and exits. See also the \f3\-showversion\fP option.
.TP 3
\-version:release
Specifies that the version specified by the release is required by the class or JAR file specified on the command line. If the version of the \f3java\fP command called does not meet this specification and an appropriate implementation is found on the system, then the appropriate implementation will be used.
.br
.br
The \f3release\fP option specifies an exact version and a list of versions called a version string. A version string is an ordered list of version ranges separated by spaces. A version range is either a \f2version\-id\fP, a \f2version\-id\fP followed by an asterisk (\f3*\fP), a \f2version\-id\fP followed by a plus sign (\f3+\fP), or a version range that consists of two \f2version\-ids\fP combined using an ampersand (\f3&\fP). The asterisk means prefix match, the plus sign means this version or greater, and the ampersand means the logical \f3and\fP of the two version\-ranges, for example:
.nf
\f3
.fl
\-version:"1.6.0_13 1.6*&1.6.0_10+"
.fl
\fP
.fi
The meaning of the previous example is that the class or JAR file requires either version 1.6.0_13, or a version with 1.6 as a \f2version\-id\fP prefix and that is not less than 1.6.0_10. The exact syntax and definition of version strings can be found in Appendix A of the \f2Java Network Launching Protocol & API Specification (JSR\-56)\fP.
.br
.br
For JAR files, the preference is to specify version requirements in the JAR file manifest rather than on the command line.
.br
.br
See \f2Notes\fP for important policy information on the use of this option.
.RE
.LP
.SS
Non\-Standard Options
.LP
.RS 3
.TP 3
\-X
Displays information about nonstandard options and exits.
.TP 3
\-Xint
Operates in interpreted\-only mode. Compilation to native code is disabled, and all bytecode is executed by the interpreter. The performance benefits offered by the Java HotSpot Client VM adaptive compiler is not present in this mode.
.TP 3
\-Xbatch
Disables background compilation. Typically, the Java VM compiles the method as a background task, running the method in interpreter mode until the background compilation is finished. The \-Xbatch flag disables background compilation so that compilation of all methods proceeds as a foreground task until completed.
.TP 3
\-Xbootclasspath:bootclasspath
Specifies a colon\-separated list of directories, JAR files, and ZIP archives to search for boot class files. These are used in place of the boot class files included in the Java platform JDK.
.br
.br
Applications that use this option for the purpose of overriding a class in rt.jar should not be deployed because doing so would contravene the Java Runtime Environment binary code license.
.TP 3
\-Xbootclasspath/a:path
Specifies a colon\-separated path of directories, JAR files, and ZIP archives to append to the default bootstrap class path.
.TP 3
\-Xbootclasspath/p:path
Specifies a colon\-separated path of directories, JAR files, and ZIP archives to add in front of the default bootstrap class path.
.br
.br
Do not deploy applications that use this option to override a class in rt.jar because this violates the Java Runtime Environment binary code license.
.TP 3
\-Xcheck:jni
Performs additional checks for Java Native Interface (JNI) functions. Specifically, the Java Virtual Machine validates the parameters passed to the JNI function and the runtime environment data before processing the JNI request. Any invalid data encountered indicates a problem in the native code, and the Java Virtual Machine will terminate with a fatal error in such cases. Expect a performance degradation when this option is used.
.TP 3
\-Xfuture
Performs strict class\-file format checks. For backward compatibility, the default format checks performed by the Java virtual machine are no stricter than the checks performed by 1.1.x versions of the JDK software. The \f3\-Xfuture\fP option turns on stricter class\-file format checks that enforce closer conformance to the class\-file format specification. Developers are encouraged to use this flag when developing new code because the stricter checks will become the default in future releases of the Java application launcher.
.TP 3
\-Xnoclassgc
Disables class garbage collection. Use of this option preven memory recovery from loaded classes thus increasing overall memory usage. This could cause \f3OutOfMemoryError\fP to be thrown in some applications.
.TP 3
\-Xincgc
Enables the incremental garbage collector. The incremental garbage collector, which is turned off by default, will reduce the occasional long garbage\-collection pauses during program execution. The incremental garbage collector will at times execute concurrently with the program and during such times will reduce the processor capacity available to the program.
.TP 3
\-Xloggc:file
Reports on each garbage collection event, as with \f3\-verbose:gc\fP, but logs this data to a file. In addition to the information \f3\-verbose:gc\fP gives, each reported event will be preceded by the time (in seconds) since the first garbage\-collection event.
.br
.br
Always use a local file system for storage of this file to avoid stalling the Java VM due to network latency. The file may be truncated in the case of a full file system and logging will continue on the truncated file. This option overrides \f3\-verbose:gc\fP when both are specified on the command line.
.TP 3
\-Xmnsize or \-XX:NewSize
Sets the size of the young generation (nursery).
.TP 3
\-Xmsn
Specifies the initial size, in bytes, of the memory allocation pool. This value must be a multiple of 1024 greater than 1 MB. Append the letter \f3k\fP or \f3K\fP to indicate kilobytes, or \f3m\fP or \f3M\fP to indicate megabytes. The default value is chosen at runtime based on system configuration. See \f2Garbage Collector Ergonomics\fP at http://docs.oracle.com/javase/7/docs/technotes/guides/vm/gc\-ergonomics.html
.br
.br
Examples:
.nf
\f3
.fl
\-Xms6291456
.fl
\-Xms6144k
.fl
\-Xms6m
.fl
\fP
.fi
.TP 3
\-Xmxn
Specifies the maximum size, in bytes, of the memory allocation pool. This value must a multiple of 1024 greater than 2 MB. Append the letter \f3k\fP or \f3K\fP to indicate kilobytes, or \f3m\fP or \f3M\fP to indicate megabytes. The default value is chosen at runtime based on system configuration.
.br
.br
For server deployments, \f3\-Xms\fP and \f3\-Xmx\fP are often set to the same value. See \f2Garbage Collector Ergonomics\fP at http://docs.oracle.com/javase/7/docs/technotes/guides/vm/gc\-ergonomics.html
.br
.br
Examples:
.nf
\f3
.fl
\-Xmx83886080
.fl
\-Xmx81920k
.fl
\-Xmx80m
.fl
\fP
.fi
On Solaris 7 and Solaris 8 SPARC platforms, the upper limit for this value is approximately 4000 m minus overhead amounts. On Solaris 2.6 and x86 platforms, the upper limit is approximately 2000 m minus overhead amounts. On Linux platforms, the upper limit is approximately 2000 m minus overhead amounts.
.TP 3
\-Xprof
Profiles the running program, and sends profiling data to standard output. This option is provided as a utility that is useful in program development and is not intended to be used in production systems.
.TP 3
\-Xrs
Reduces use of operating\-system signals by the Java VM.
.br
.br
In an earlier release, the Shutdown Hooks facility was added to enable orderly shutdown of a Java application. The intent was to enable user cleanup code (such as closing database connections) to run at shutdown, even if the Java VM terminates abruptly.
.br
.br
The Java VM catches signals to implement shutdown hooks for unexpected Java VM termination. The Java VM uses \f3SIGHUP\fP, \f3SIGINT\fP, and \f3SIGTERM\fP to initiate the running of shutdown hooks.
.br
.br
The JVM uses a similar mechanism to implement the feature of dumping thread stacks for debugging purposes. The JVM uses \f3SIGQUIT\fP to perform thread dumps.
.br
.br
Applications embedding the Java VM frequently need to trap signals such as \f3SIGINT\fP or \f3SIGTERM\fP, which can lead to interference with the Java VM signal handlers. The \f3\-Xrs\fP command\-line option is available to address this issue. When \f3\-Xrs\fP is used on the Java VM, the signal masks for \f3SIGINT\fP, \f3SIGTERM\fP, \f3SIGHUP\fP, and \f3SIGQUIT\fP are not changed by the Java VM, and signal handlers for these signals are not installed.
.br
.br
There are two consequences of specifying \f3\-Xrs\fP:
.RS 3
.TP 2
o
\f3SIGQUIT\fP thread dumps are not available.
.TP 2
o
User code is responsible for causing shutdown hooks to run, for example by calling \f3System.exit()\fP when the Java VM is to be terminated.
.RE
.TP 3
\-Xssn
Sets the thread stack size.
.TP 3
\-XX:AllocationPrefetchStyle=n
Sets the style of prefetch used during allocation. default=2.
.TP 3
\-XX:+AggressiveOpts
Enables aggressive optimization.
.TP 3
\-XX:+|\-DisableAttachMechanism
Specifies whether commands (such as \f3jmap\fP and \f3jconsole\fP) can attach to the Java VM. By default, this feature is disabled. That is, attaching is enabled, for example:
.nf
\f3
.fl
java \-XX:+DisableAttachMechanism
.fl
\fP
.fi
.TP 3
\-XX:+|\-FlightRecorder
Toggles the use of the Java Flight Recorder (JFR) during the runtime of the application. This is a commercial feature that requires you to also specify the \f3\-XX:+UnlockCommercialFeatures\fP option as follows:
.nf
\f3
.fl
java \-XX:+UnlockCommercialFeatures \-XX:+FlightRecorder
.fl
\fP
.fi
.TP 3
\-XX:FlightRecorderOptions=parameter=value
Sets the parameters that control the behavior of JFR. This option can be used only when JFR is enabled (that is, the \f3\-XX:+FlightRecorder\fP option is specified).
.br
.br
The following list contains all available JFR parameters:
.RS 3
.TP 3
defaultrecording=true|false
Specifies whether background recording is enabled. By default, this parameter is set to \f3false\fP (background recording is disabled). To enable it, set the parameter to \f3true\fP.
.TP 3
disk=true|false
Specifies whether JFR should write a continuous recording to disk. By default, this parameter is set to \f3false\fP (continuous recording to disk is disabled). To enable it, set the parameter to \f3true\fP.
.TP 3
dumponexit=true|false
Specifies whether a dump file of JFR data should be generated when the JVM terminates in a controlled manner. By default, this parameter is set to \f3false\fP (dump file on exit is not generated). To enable it, set the parameter to \f3true\fP.
.br
.br
The dump file is written to the location defined by the \f3dumponexitpath\fP parameter.
.TP 3
dumponexitpath=path
Specifies the path and name of the dump file with JFR data that is created when the JVM exits in a controlled manner if you set the \f3dumponexit=true\fP parameter.If the specified path is a directory, the JVM assigns a file name that shows the creation date and time. If the specified path includes a file name and if that file already exists, the JVM creates a new file by appending the date and time stamp to the specified file name.
.TP 3
globalbuffersize=size
Specifies the total amount of primary memory (in MB) used for data retention. By default, the size is set to 10 MB.
.TP 3
maxage=time
Specifies the maximum age (in minutes) of disk data for default recording. By default, the maximum age is set to 15 minutes.This parameter is valid only if you set the \f3disk=true\fP parameter.
.TP 3
maxchunksize=size
Specifies the maximum size (in MB) of the data chunks in a recording. By default, the maximum size of data chunks is set to 12 MB.
.TP 3
maxsize=size
Specifies the maximum size (in MB) of disk data for default recording. By default, the maximum size of disk data is not limited.
.br
.br
This parameter is valid only if you set the \f3disk=true\fP parameter.
.TP 3
repository=path
Specifies the repository (a directory) for temporary disk storage. By default, the system’s temporary directory is used.
.TP 3
settings=path
Specifies the path and name of the event settings file (of type JFS). By default, the \f3default.jfs\fP file is used, which is located in \f3JAVA_HOME/jre/lib/jfr\fP.
.TP 3
threadbuffersize=size
Specifies the per\-thread local buffer size (in KB). Higher values for this parameter allow more data gathering without contention to flush it to the global storage. It can increase application footprint in a thread\-rich environment. By default, the local buffer size is set to 5 KB.
.br
.br
You can specify values for multiple parameters by separating them with a comma. For example, to instruct JFR to write a continuous recording to disk, and set the maximum size of data chunks to 10 MB, specify the following:
.nf
\f3
.fl
\-XX:FlightRecorderOptions=disk=true,maxchunksize=10M
.fl
\fP
.fi
.RE
.TP 3
\-XXLargePageSizeInBytes=n
Specifies the maximum size for large pages.
.TP 3
\-XX:MaxGCPauseMillis=n
Sets a target for the maximum GC pause time. This is a soft goal, and the Java VM will make its best effort to achieve it. There is no maximum value set by default.
.TP 3
\-XX:NewSize
Sets the size of the young generation (nursery). Sames as \f3\-Xmnsize\fP.
.TP 3
\-XX:ParallelGCThreads=n
Sets the number of GC threads in the parallel collectors.
.TP 3
\-XX:PredictedClassLoadCount=n
This option requires that the \f3UnlockExperimentalVMOptions\fP flag be set first. Use the \f3PredictedClassLoadCount\fP flag if your application loads a lot of classes and especially if \f3class.forName()\fP is used heavily. The recommended value is the number of classes loaded as shown in the output from \f3\-verbose:class\fP.
.br
.br
Example:
.nf
\f3
.fl
java \-XX:+UnlockExperimentalVMOptions \-XX:PredictedClassLoadCount=60013
.fl
\fP
.fi
.TP 3
\-XX:+PrintCompilation
Prints verbose output from the Java HotSpot VM dynamic runtime compiler.
.TP 3
\-XX:+PrintGCDetails \-XX:+PrintGCTimeStamps
Prints garbage collection output along with time stamps.
.TP 3
\-XX:SoftRefLRUPolicyMSPerMB=0
This flag enables aggressive processing of software references. Use this flag if the software reference count has an impact on the Java HotSpot VM garbage collector.
.TP 3
\-XX:StartFlightRecording=parameter=value
Starts a JFR recording for the Java application. This option is equivalent to the \f3start_flightrecording\fP diagnostic command that starts JFR at runtime. You can set the following parameters when starting a JFR recording:
.RS 3
.TP 3
compress=true|false
Specifies whether to compress the JFR recording log file (of type JFR) on the disk using the \f3gzip\fP file compression utility. This parameter is valid only if the \f3filename\fP parameter is specified. By defaut it is set to \f3false\fP (recoding is not compressed). To enable compression, set the parameter to \f3true\fP.
.TP 3
defaultrecording=true|false
Specifies whether the recording is continuous or it runs for a limited time. By default, this parameter is set to \f3false\fP (recording runs for a limited time). To make the recording run continuously, set the parameter to \f3true\fP.
.TP 3
delay=time
Specifies the delay (in milliseconds) between the Java application launch time and the start of the recording. By default, there is no delay and this parameter is set to 0.
.TP 3
duration=time
Specifies the duration (in milliseconds) of the recording. By default, the duration is not limited.
.TP 3
filename=path
Specifies the path and name of the JFR recording log file.
.TP 3
name=identifier
Specifies the identifier for the JFR recording. By default, it is set to Recording x
.TP 3
maxage=time
Specifies the maximum age (in minutes) of disk data for default recording. By default, the maximum age is set to 15 minutes.
.TP 3
maxsize=size
Specifies the maximum size (in MB) of the recording before it is flushed from the thread buffer to the global buffer. By default, the maximum size is not limited.
.br
.br
This parameter is valid only for size\-bound recordings.
.TP 3
settings=path
Specifies the path and name of the event settings file (of type JFS). By default, the \f3default.jfs\fP file is used, which is located in \f3JAVA_HOME/jre/lib/jfr\fP.
.RE
You can specify values for multiple parameters by separating them with a comma. For example, to save the recording to test.jfr in the current working directory, and instruct JFR to compress the log file, specify the following:
.nf
\f3
.fl
\-XX:StartFlightRecording=filename=test.jfr,compress=true
.fl
\fP
.fi
.RE
.LP
.RS 3
.TP 3
\-XX:TLABSize=n
Thread local allocation buffers (TLAB) are enabled by default in the Java HotSpot VM. The Java HotSpot VM sizes TLABs based on allocation patterns. The \f3\-XX:TLABSize\fP option enables fine\-tuning the size of TLABs.
.TP 3
\-XX:+UnlockCommercialFeatures
Use this flag to actively unlock the use of commercial features. Commercial features are the products Oracle Java SE Advanced or Oracle Java SE Suite, as defined at the Java SE Products web page.
.br
.br
If this flag is not specified, then the default is to run the Java Virtual Machine without the commercial features being available. After they are enabled, it is not possible to disable their use at runtime.
.TP 3
\-XX:+UseAltSigs
The Java VM uses \f3SIGUSR1\fP and \f3SIGUSR2\fP by default, which can sometimes conflict with applications that signal\-chain \f3SIGUSR1\fP and \f3SIGUSR2\fP. The \f3\-XX:+UseAltSigs\fP option causes the Java VM to use signals other than \f3SIGUSR1\fP and \f3SIGUSR2\fP as the default.
.TP 3
\-XX:+|\-UseCompressedOops
Enables compressed references in 64\-bit Java VMs.
.br
.br
This option is true by default.
.TP 3
\-XX:+UseConcMarkSweepGC or \-XX:+UseG1GC
Enables either the Concurrent Mark Sweep (CMS) or the G1 garbage collectors.
.TP 3
\-XX:+|\-UseLargePages
Enables large page support.
.br
.br
Large pages are enabled by default on Solaris.
.TP 3
\-XX:+UseParallelOldGC
Enables the parallel garbage collectors, which are optimized for throughput and average response time.
.RE
.LP
.SH "NOTES"
.LP
.LP
The \f2\-version:release\fP option places no restrictions on the complexity of the release specification. However, only a restricted subset of the possible release specifications represent sound policy and only these are fully supported. These policies are:
.LP
.RS 3
.TP 3
1.
Any version, represented by not using this option.
.TP 3
2.
Any version greater than an arbitrarily precise \f2version\-i\fPd value, for example:
.nf
\f3
.fl
"1.6.0_10+"
.fl
\fP
.fi
This would utilize any version greater than 1.6.0_10. This is useful for a case where an interface was introduced (or a bug fixed) in the release specified.
.TP 3
3.
A version greater than an arbitrarily precise version\-id, bounded by the upper bound of that release family, for example:
.nf
\f3
.fl
"1.6.0_10+&1.6*"
.fl
\fP
.fi
.TP 3
4.
An \f3or\fP expressions of items 2 or 3, for example:
.nf
\f3
.fl
"1.6.0_10+&1.6* 1.7+"
.fl
\fP
.fi
Similar to item 2. This is useful when a change was introduced in a release (1.7) but also made available in updates to earlier releases.
.RE
.LP
.SH "Performance Tuning Examples"
.LP
.LP
The following examples show how to use experimental tuning flags to optimize either throughput or faster response time.
.LP
.SS
Example 1, Tuning for Higher Throughput
.LP
.nf
\f3
.fl
java \-d64 \-server \-XX:+AggressiveOpts \-XX:+UseLargePages \-Xmn10g \-Xms26g \-Xmx26g
.fl
\fP
.fi
.LP
.SS
Example 2, Tuning for Lower Response Time
.LP
.nf
\f3
.fl
java \-d64 \-XX:+UseG1GC \-Xms26g Xmx26g \-XX:MaxGCPauseMillis=500 \-XX:+PrintGCTimeStamps
.fl
\fP
.fi
.LP
.SH "EXIT STATUS"
.LP
.LP
The following exit values are typically returned by the launcher, typically when the launcher is called with the wrong arguments, serious errors, or exceptions thrown from the Java Virtual Machine. However, a Java application may choose to return any value using the API call \f3System.exit(exitValue)\fP.
.LP
.RS 3
.TP 2
o
\f30\fP: Successful completion
.TP 2
o
\f3>0\fP: An error occurred
.RE
.LP
.SH "SEE ALSO"
.LP
.RS 3
.TP 2
o
javac(1)
.TP 2
o
jdb(1)
.TP 2
o
javah(1)
.TP 2
o
jar(1)
.RE
.LP

203
desktop/test-osx/Tick's Tales.app/Contents/MacOS/jre/man/man1/javaws.1 Normal file
View File

@@ -0,0 +1,203 @@
." Copyright (c) 2003, 2011, Oracle and/or its affiliates. All rights reserved.
."
.TH javaws 1 "18 Jul 2013"
.LP
.SH "Name"
\f2javaws\fP Command Line
.LP
.SH "NAME"
.LP
.LP
\f2javaws\fP \- Java Web Start launcher command
.LP
.SH "SYNOPSIS"
.LP
.LP
\f2javaws [run\-options] <jnlp>\fP
.LP
.LP
\f2javaws [control\-options]\fP
.LP
.SH "PARAMETERS"
.LP
.LP
\f2[run\-options]\fP
.LP
.LP
Command\-line run\-options. run\-options may be in any order. For a discussion of the various run\-options, see RUN\-OPTIONS below.
.LP
.LP
\f2<jnlp>\fP
.LP
.LP
This can be either the path of, or the Uniform Resource Locater (URL) of the JNLP (Java Network Launching Protocol) file.
.LP
.LP
\f2[control\-options]\fP
.LP
.LP
Command\-line control\-options. control\-options may be in any order. For a discussion of the various control\-options, see CONTROL\-OPTIONS below.
.LP
.SH "DESCRIPTION"
.LP
.LP
The \f2javaws\fP command launches Java Web Start, which is the reference implementation of the Java Network Launching Protocol (JNLP). Java Web Start launches Java applications/applets hosted on a network.
.LP
.LP
If a JNLP file is specified, \f2javaws\fP will launch the Java application/applet specified in the JNLP file.
.LP
.LP
The \f2javaws\fP launcher has a set of options that are supported in the current release. However, the options may be removed in a future release.
.LP
.SH "RUN\-OPTIONS"
.LP
.LP
\f2\-offline\fP
.LP
.LP
Run Java Web Start in offline mode.
.LP
.LP
\f2\-Xnosplash\fP
.LP
.LP
Do not display the initial splash screen.
.LP
.LP
\f2\-open <arguments>\fP
.LP
.LP
If specified, replaces the arguments in the jnlp file with \f2\-open <arguments>\fP.
.LP
.LP
\f2\-print <arguments>\fP
.LP
.LP
If specified, replaces the arguments in the jnlp file with \f2\-print <arguments>\fP.
.LP
.LP
\f2\-online\fP
.LP
.LP
Use online mode (default behavior).
.LP
.LP
\f2\-wait\fP
.LP
.LP
If specified, the \f2javaws\fP process will not exit until the application exits. This option does not function as described on Windows platforms.
.LP
.LP
\f2\-verbose\fP
.LP
.LP
Display additional output.
.LP
.LP
\f2\-J<option>\fP
.LP
.LP
Supply options to the VM.
.LP
.LP
\f2\-system\fP
.LP
.LP
Run the application from the system cache only.
.LP
.SH "CONTROL\-OPTIONS"
.LP
.LP
\f2\-viewer\fP
.LP
.LP
Show the Cache Viewer in the Java Control Panel.
.LP
.LP
\f2\-clearcache\fP
.LP
.LP
Remove all non\-installed applications from the cache.
.LP
.LP
\f2\-userConfig <property name>\fP
.LP
.LP
Clear the specified deployment property.
.LP
.LP
\f2\-userConfig <property name> <property value>\fP
.LP
.LP
Set the specified deployment property to the specified value.
.LP
.LP
\f2\-uninstall\fP
.LP
.LP
Remove all applications from the cache.
.LP
.LP
\f2\-uninstall <jnlp>\fP
.LP
.LP
Remove the application from the cache.
.LP
.LP
\f2\-import [import\-options] <jnlp>\fP
.LP
.LP
Import the application to the cache.
.LP
.SH "IMPORT\-OPTIONS"
.LP
.LP
\f2\-silent\fP
.LP
.LP
Import silently (with no user interface).
.LP
.LP
\f2\-system\fP
.LP
.LP
Import application to the system cache.
.LP
.LP
\f2\-codebase <url>\fP
.LP
.LP
Retrieve resources from the given codebase.
.LP
.LP
\f2\-shortcut\fP
.LP
.LP
Install shortcuts as if user allowed prompt. This option has no effect unless \f2\-silent\fP option is also used.
.LP
.LP
\f2\-association\fP
.LP
.LP
Install associations as if user allowed prompt. This option has no effect unless \f2\-silent\fP option is also used.
.LP
.SH "FILES"
.LP
.LP
For information about the user and system cache and deployment.properties files, see
.na
\f2System\- and User\-Level Properties\fP @
.fi
http://docs.oracle.com/javase/7/docs/technotes/guides/deployment/deployment\-guide/properties.html.
.LP
.SH "MORE INFORMATION"
.LP
.LP
For more information about Java Web Start, see
.na
\f2Java Web Start\fP @
.fi
http://docs.oracle.com/javase/7/docs/technotes/guides/javaws/index.html.
.LP

1748
desktop/test-osx/Tick's Tales.app/Contents/MacOS/jre/man/man1/keytool.1 Normal file
View File

File diff suppressed because it is too large Load Diff

349
desktop/test-osx/Tick's Tales.app/Contents/MacOS/jre/man/man1/orbd.1 Normal file
View File

@@ -0,0 +1,349 @@
." Copyright (c) 2001, 2011, Oracle and/or its affiliates. All rights reserved.
."
.TH orbd 1 "18 Jul 2013"
.LP
.SH "Name"
orbd \- The Object Request Broker Daemon
.LP
.LP
\f3orbd\fP is used to enable clients to transparently locate and invoke persistent objects on servers in the CORBA environment.
.LP
.LP
\f3See also:\fP
.na
\f2Naming Service\fP @
.fi
http://docs.oracle.com/javase/7/docs/technotes/guides/idl/jidlNaming.html
.LP
.SH "SYNOPSIS"
.LP
.nf
\f3
.fl
orbd <\fP\f3options\fP\f3>
.fl
\fP
.fi
.LP
.SH "DESCRIPTION"
.LP
.LP
The Server Manager included with the \f3orbd\fP tool is used to enable clients to transparently locate and invoke persistent objects on servers in the CORBA environment. The persistent servers, while publishing the persistent object references in the Naming Service, include the port number of the ORBD in the object reference instead of the port number of the Server. The inclusion of an ORBD port number in the object reference for persistent object references has the following advantages:
.LP
.RS 3
.TP 2
o
The object reference in the Naming Service remains independent of the server life cycle. For example, the object reference could be published by the server in the Naming Service when it is first installed, and then, independent of how many times the server is started or shutdown, the ORBD will always return the correct object reference to the invoking client.
.TP 2
o
The client needs to lookup the object reference in the Naming Service only once, and can keep re\-using this reference independent of the changes introduced due to server life cycle.
.RE
.LP
.LP
To access ORBD's Server Manager, the server must be started using servertool(1), which is a command\-line interface for application programmers to register, unregister, startup, and shutdown a persistent server. For more information on the Server Manager, see the section in this document titled \f2Server Manager\fP.
.LP
.LP
When \f2orbd\fP starts up, it also starts a naming service. For more information on the naming service, link to
.na
\f2Naming Service\fP @
.fi
http://docs.oracle.com/javase/7/docs/technotes/guides/idl/jidlNaming.html.
.LP
.SH "OPTIONS"
.LP
.SS
Required Options
.LP
.RS 3
.TP 3
\-ORBInitialPort nameserverport
Specifies the port on which the name server should be started. Once started, \f2orbd\fP will listen for incoming requests on this port. Note that when using Solaris software, you must become root to start a process on a port under 1024. For this reason, we recommend that you use a port number greater than or equal to 1024. (required)
.RE
.LP
.LP
.LP
.SS
OTHER OPTIONS
.LP
.RS 3
.TP 3
\-port port
Specifies the activation port where ORBD should be started, and where ORBD will be accepting requests for persistent objects. The default value for this port is 1049. This port number is added to the port field of the persistent Interoperable Object References (IOR). (optional)
.RE
.LP
.RS 3
.TP 3
\-defaultdb directory
Specifies the base where the ORBD persistent storage directory \f2orb.db\fP is created. If this option is not specified, the default value is "./orb.db". (optional)
.RE
.LP
.RS 3
.TP 3
\-serverPollingTime milliseconds
Specifies how often ORBD checks for the health of persistent servers registered via \f2servertool\fP. The default value is 1,000 ms. The value specified for \f2milliseconds\fP must be a valid positive integer. (optional)
.RE
.LP
.RS 3
.TP 3
\-serverStartupDelay milliseconds
Specifies how long ORBD waits before sending a location forward exception after a persistent server that is registered via \f2servertool\fP is restarted. The default value is 1,000 ms. The value specified for \f2milliseconds\fP must be a valid positive integer. (optional)
.RE
.LP
.RS 3
.TP 3
\-Joption
Pass \f2option\fP to the Java virtual machine, where \f2option\fP is one of the options described on the reference page for java(1). For example, \f3\-J\-Xms48m\fP sets the startup memory to 48 megabytes. It is a common convention for \f3\-J\fP to pass options to the underlying virtual machine.
.TP 3
.RE
.LP
.SH "Starting and Stopping the Naming Service"
.LP
.LP
A Naming Service is a CORBA service that allows
.na
\f2CORBA objects\fP @
.fi
http://docs.oracle.com/javase/7/docs/technotes/guides/idl/jidlGlossary.html#CORBA%20object to be named by means of binding a name to an object reference. The
.na
\f2name binding\fP @
.fi
http://docs.oracle.com/javase/7/docs/technotes/guides/idl/jidlGlossary.html#name%20binding may be stored in the naming service, and a client may supply the name to obtain the desired object reference.
.LP
.LP
Prior to running a client or a server, you will start ORBD. ORBD includes a persistent Naming Service and a transient Naming Service, both of which are an implementation of the COS Naming Service.
.LP
.LP
The \f4Persistent\fP\f3 Naming Service\fP provides persistence for naming contexts. This means that this information is persistent across service shutdowns and startups, and is recoverable in the event of a service failure. If ORBD is restarted, the Persistent Naming Service will restore the naming context graph, so that the binding of all clients' and servers' names remains intact (persistent).
.LP
.LP
\
.LP
.LP
For backward compatibility, \f2tnameserv\fP, a \f4Transient\fP\f3 Naming Service\fP shipped with older versions of the JDK, is also included in this release of J2SE. A transient naming service retains naming contexts as long as it is running. If there is a service interruption, the naming context graph is lost.
.LP
.LP
The \f2\-ORBInitialPort\fP argument is a required command\-line argument for \f2orbd\fP, and is used to set the port number on which the Naming Service will run. The following instructions assume you can use port 1050 for the Java\ IDL Object Request Broker Daemon. When using Solaris software, you must become root to start a process on a port under 1024. For this reason, we recommend that you use a port number greater than or equal to 1024. You can substitute a different port if necessary.
.LP
.LP
To start \f2orbd\fP from a UNIX command shell, enter:
.LP
.nf
\f3
.fl
orbd \-ORBInitialPort 1050&
.fl
\fP
.fi
.LP
.LP
From an MS\-DOS system prompt (Windows), enter:
.LP
.nf
\f3
.fl
start orbd \-ORBInitialPort 1050
.fl
\fP
.fi
.LP
.LP
Now that ORBD is running, you can run your server and client applications. When running the client and server applications, they must be made aware of the port number (and machine name, if applicable) where the Naming Service is running. One way to do this is to add the following code to your application:
.LP
.nf
\f3
.fl
Properties props = new Properties();
.fl
props.put("org.omg.CORBA.ORBInitialPort", "1050");
.fl
props.put("org.omg.CORBA.ORBInitialHost", "MyHost");
.fl
ORB orb = ORB.init(args, props);
.fl
\fP
.fi
.LP
.LP
In this example, the Naming Service is running on port 1050 on host "MyHost". Another way is to specify the port number and/or machine name when running the server or client application from the command line. For example, you would start your "HelloApplication" with the following command line:
.LP
.nf
\f3
.fl
java HelloApplication \-ORBInitialPort 1050 \-ORBInitialHost MyHost
.fl
\fP
.fi
.LP
.LP
To stop the naming service, use the relevant operating system command, such as \f2pkill orbd\fP on Solaris, or \f2Ctrl+C\fP in the DOS window in which \f2orbd\fP is running. Note that names registered with the naming service may disappear when the service is terminated if the naming service is transient. The Java IDL naming service will run until it is explicitly stopped.
.LP
.LP
For more information on the Naming Service included with ORBD, see
.na
\f2Naming Service\fP @
.fi
http://docs.oracle.com/javase/7/docs/technotes/guides/idl/jidlNaming.html.
.LP
.SH "Server Manager"
.LP
.LP
To access ORBD's Server Manager and run a persistent server, the server must be started using servertool(1), which is a command\-line interface for application programmers to register, unregister, startup, and shutdown a persistent server. When a server is started using \f2servertool\fP, it must be started on the same host and port on which \f2orbd\fP is executing. If the server is run on a different port, the information stored in the database for local contexts will be invalid and the service will not work properly.
.LP
.SS
Server Manager: an Example
.LP
.LP
Using the
.na
\f2sample tutorial\fP @
.fi
http://docs.oracle.com/javase/7/docs/technotes/guides/idl/jidlExample.html for our demonstration, you would run the \f2idlj\fP compiler and \f2javac\fP compiler as shown in the tutorial. To run the Server Manager, follow these steps for running the application:
.LP
.LP
Start \f2orbd\fP.
.LP
.LP
To start \f2orbd\fP from a UNIX command shell, enter:
.LP
.LP
\
.LP
.nf
\f3
.fl
orbd \-ORBInitialPort 1050
.fl
\fP
.fi
.LP
.LP
From an MS\-DOS system prompt (Windows), enter:
.LP
.nf
\f3
.fl
start orbd \-ORBInitialPort 1050
.fl
\fP
.fi
.LP
.LP
Note that \f21050\fP is the port on which you want the name server to run. \f2\-ORBInitialPort\fP is a required command\-line argument. When using Solaris software, you must become root to start a process on a port under 1024. For this reason, we recommend that you use a port number greater than or equal to 1024.
.LP
.LP
Start the \f2servertool\fP:
.LP
.LP
To start the Hello server, enter:
.LP
.nf
\f3
.fl
servertool \-ORBInitialPort 1050
.fl
\fP
.fi
.LP
.LP
Make sure the name server (\f2orbd\fP) port is the same as in the previous step, for example, \f2\-ORBInitialPort 1050\fP. The \f2servertool\fP must be started on the same port as the name server.
.LP
.LP
The \f2servertool\fP command line interface appears.
.LP
.LP
.LP
.LP
Start the Hello server from the \f2servertool\fP prompt:
.LP
.nf
\f3
.fl
servertool > register \-server HelloServer \-classpath . \-applicationName
.fl
HelloServerApName
.fl
\fP
.fi
.LP
.LP
The \f2servertool\fP registers the server, assigns it the name of "HelloServerApName", and displays its server id, along with a listing of all registered servers.
.LP
.LP
.LP
.LP
Run the client application from another terminal window or prompt:
.LP
.LP
\
.LP
.nf
\f3
.fl
java HelloClient \-ORBInitialPort 1050 \-ORBInitialHost localhost
.fl
\fP
.fi
.LP
.LP
For this example, you can omit \f2\-ORBInitialHost localhost\fP since the name server is running on the same host as the Hello client. If the name server is running on a different host, use \f2\-ORBInitialHost\fP \f2nameserverhost\fP to specify the host on which the IDL name server is running.
.LP
.LP
Specify the name server (\f2orbd\fP) port as done in the previous step, for example, \f2\-ORBInitialPort 1050\fP.
.LP
.LP
\
.LP
.LP
\
.LP
.LP
When you have finished experimenting with the Server Manager, be sure to shut down or kill the name server (\f2orbd\fP) and \f2servertool\fP.
.LP
.LP
To shut down \f2orbd\fP from a DOS prompt, select the window that is running the server and enter \f2Ctrl+C\fP to shut it down. To shut down \f2orbd\fPfrom a Unix shell, find the process, and kill it. The server will continue to wait for invocations until it is explicitly stopped.
.LP
.LP
To shut down the \f2servertool\fP, type \f2quit\fP and press the \f2Enter\fP key on the keyboard.
.LP
.SH "See Also"
.LP
.RS 3
.TP 2
o
.na
\f2Naming Service\fP @
.fi
http://docs.oracle.com/javase/7/docs/technotes/guides/idl/jidlNaming.html
.br
.TP 2
o
servertool(1)
.RE
.LP
.br
.LP

324
desktop/test-osx/Tick's Tales.app/Contents/MacOS/jre/man/man1/pack200.1 Normal file
View File

@@ -0,0 +1,324 @@
." Copyright (c) 2004, 2011, Oracle and/or its affiliates. All rights reserved.
."
.TH pack200 1 "18 Jul 2013"
.LP
.SH "Name"
pack200 \- JAR Packing tool
.LP
.SH "SYNOPSIS"
.LP
.LP
\f4pack200\fP\f2 [ \fP\f2options\fP ] \f2output\-file\fP \f2JAR\-file\fP
.LP
.LP
Options may be in any order. The last option on the command line or in a properties file supersedes all previously specified options.
.LP
.RS 3
.TP 3
options
Command\-line options.
.TP 3
output\-file
Name of the output file.
.TP 3
JAR\-file
Name of the input file.
.RE
.LP
.SH "DESCRIPTION"
.LP
.LP
The \f2pack200\fP tool is a Java application that transforms a JAR file into a compressed \f2pack200\fP file using the Java \f2gzip\fP compressor. The \f2pack200\fP files are highly compressed files that can be directly deployed, saving bandwidth and reducing download time.
.LP
.LP
The \f2pack200\fP tool uses several options to fine\-tune and set the compression engine.
.LP
.SS
Typical usage:
.LP
.LP
\f2% pack200 myarchive.pack.gz myarchive.jar\fP
.LP
.LP
In this example, \f2myarchive.pack.gz\fP is produced using the default \f2pack200\fP settings.
.LP
.SH "OPTIONS"
.LP
.LP
\f4\-r \-\-repack\fP
.LP
.LP
Produces a JAR file by packing the file \f2myarchive.jar\fP and unpacking it. The resulting file can be used as an input to the \f2jarsigner(1)\fP tool.
.LP
.LP
\f2% pack200 \-\-repack myarchive\-packer.jar myarchive.jar\fP
.LP
.LP
\f2% pack200 \-\-repack myarchive.jar\fP
.LP
.LP
\f4\-g \-\-no\-gzip\fP
.LP
.LP
Produces a \f2pack200\fP file. With this option a suitable compressor must be used, and the target system must use a corresponding decompresser.
.LP
.LP
\f2% pack200 \-\-no\-gzip myarchive.pack myarchive.jar\fP
.LP
.LP
\f4\-G \-\-strip\-debug\fP
.LP
.LP
Strips attributes used for debugging from the output. These include \f2SourceFile\fP, \f2LineNumberTable\fP, \f2LocalVariableTable\fP and \f2LocalVariableTypeTable\fP. Removing these attributes reduces the size of both downloads and installations but reduces the usefulness of debuggers.
.LP
.LP
\f4\-\-keep\-file\-order\fP
.LP
.LP
Preserve the order of files in the input file; this is the default behavior.
.LP
.LP
\f4\-O \-\-no\-keep\-file\-order\fP
.LP
.LP
The packer will reorder and transmit all elements. Additionally, the packer may remove JAR directory names. This will reduce the download size; however, certain JAR file optimizations, such as indexing, may not work correctly.
.LP
.LP
\f4\-Svalue \-\-segment\-limit=\fP\f2value\fP
.LP
.LP
The value is the estimated target size N (in bytes) of each archive segment. If a single input file requires
.br
more than N bytes, it will be given its own archive segment. As a special case, a value of \f2\-1\fP will produce a single large segment with all input files, while a value of \f20\fP will produce one segment for each class. Larger archive segments result in less fragmentation and better compression, but processing them requires more memory.
.LP
.LP
The size of each segment is estimated by counting the size of each input file to be transmitted in the segment, along with the size of its name and other transmitted properties.
.LP
.LP
The default is \-1, which means the packer will always create a single segment output file. In cases where extremely large output files are generated, users are strongly encouraged to use segmenting or break up the input file into smaller JARs.
.LP
.LP
A 10MB JAR packed without this limit will typically pack about 10% smaller, but the packer may require a larger Java heap (about ten times the segment limit).
.LP
.LP
\f4\-Evalue \-\-effort=\fP\f2value\fP
.LP
.LP
If the value is set to a single decimal digit, the packer will use the indicated amount of effort in compressing the archive. Level \f21\fP may produce somewhat larger size and faster compression speed, while level \f29\fP will take much longer but may produce better compression. The special value \f20\fP instructs the packer to copy through the original JAR file directly with no compression. The JSR 200 standard requires any unpacker to understand this special case as a pass\-through of the entire archive.
.LP
.LP
The default is \f25\fP, investing a modest amount of time to produce reasonable compression.
.LP
.LP
\f4\-Hvalue \-\-deflate\-hint=\fP\f2value\fP
.LP
.LP
Overrides the default, which preserves the input information, but may cause the transmitted archive to be larger. The possible values are:
.LP
.RS 3
.TP 3
true
.TP 3
false
In either case, the packer will set the deflation hint accordingly in the output archive, and will not transmit the individual deflation hints of archive elements.
.RE
.LP
.RS 3
.TP 3
keep
Preserve deflation hints observed in the input JAR. (This is the default.)
.RE
.LP
.LP
\f4\-mvalue \-\-modification\-time=\fP\f2value\fP
.LP
.LP
The possible values are:
.LP
.RS 3
.TP 3
latest
The packer will attempt to determine the latest modification time, among all the available entries in the original archive, or the latest modification time of all the available entries in that segment. This single value will be transmitted as part of the segment and applied to all the entries in each segment. This can marginally decrease the transmitted size of the archive at the expense of setting all installed files to a single date.
.TP 3
keep
Preserves modification times observed in the input JAR. (This is the default.)
.RE
.LP
.LP
\f4\-Pfile \-\-pass\-file=\fP\f2file\fP
.LP
.LP
Indicates that a file should be passed through bytewise with no compression. By repeating the option, multiple files may be specified. There is no pathname transformation, except that the system file separator is replaced by the JAR file separator "\f2/\fP". The resulting file names must match exactly as strings with their occurrences in the JAR file. If file is a directory name, all files under that directory will be passed.
.LP
.LP
\f4\-Uaction \-\-unknown\-attribute=\fP\f2action\fP
.LP
.LP
Overrides the default behavior; i.e., the class file containing the unknown attribute will be passed through with the specified action. The possible values for actions are:
.LP
.RS 3
.TP 3
error
The \f2pack200\fP operation as a whole will fail with a suitable explanation.
.TP 3
strip
The attribute will be dropped. Note: Removing the required VM attributes may cause Class Loader failures.
.TP 3
pass
Upon encountering this attribute, the entire class will be transmitted as though it is a resource.
.RE
.LP
.LP
\f4\-Cattribute\-name=\fP\f2layout\fP \f3\-\-class\-attribute=\fP\f2attribute\-name=action\fP
.br
\f4\-Fattribute\-name=\fP\f2layout\fP \f3\-\-field\-attribute=\fP\f2attribute\-name=action\fP
.br
\f4\-Mattribute\-name=\fP\f2layout\fP \f3\-\-method\-attribute=\fP\f2attribute\-name=action\fP
.br
\f4\-Dattribute\-name=\fP\f2layout\fP \f3\-\-code\-attribute=\fP\f2attribute\-name=action\fP
.LP
.LP
With the above four options, the attribute layout can be specified for a class entity, such as Class attribute, Field attribute, Method attribute, and Code attribute. The attribute\-name is the name of the attribute for which the layout or action is being defined. The possible values for action are:
.LP
.RS 3
.TP 3
some\-layout\-string
The layout language is defined in the JSR 200 specification.
.LP
Example: \f2\-\-class\-attribute=SourceFile=RUH\fP
.TP 3
error
Upon encountering this attribute, the pack200 operation will fail with a suitable explanation.
.TP 3
strip
Upon encountering this attribute, the attribute will be removed from the output. Note: removing VM\-required attributes may cause Class Loader failures.
.TP 3
pass
Upon encountering this attribute, the entire class will be transmitted as though it is a resource.
.RE
.LP
.LP
Example: \f2\-\-class\-attribute=CompilationID=pass\fP will cause the class file containing the attribute \f2CompilationID\fP to be passed through without further action by the packer.
.LP
.LP
\f4\-f\fP\f2 \fP\f2pack.properties\fP \f3\-\-config\-file=\fP\f2pack.properties\fP
.LP
.LP
A configuration file, containing Java properties to initialize the packer, may be specified on the command line.
.LP
.LP
\f2% pack200 \-f pack.properties myarchive.pack.gz myarchive.jar\fP
.br
\f2% more pack.properties\fP
.br
\f2# Generic properties for the packer.\fP
.br
\f2modification.time=latest\fP
.br
\f2deflate.hint=false\fP
.br
\f2keep.file.order=false\fP
.br
\f2# This option will cause the files bearing new attributes to\fP
.br
\f2# be reported as an error rather than passed uncompressed.\fP
.br
\f2unknown.attribute=error\fP
.br
\f2# Change the segment limit to be unlimited.\fP
.br
\f2segment.limit=\-1\fP
.LP
.LP
\f4\-v \-\-verbose\fP
.LP
.LP
Outputs minimal messages. Multiple specification of this option will output more verbose messages.
.LP
.LP
\f4\-q \-\-quiet\fP
.LP
.LP
Specifies quiet operation with no messages.
.LP
.LP
\f4\-lfilename \-\-log\-file=\fP\f2filename\fP
.LP
.LP
Specifies a log file to output messages.
.LP
.LP
\f4\-? \-h \-\-help\fP
.LP
.LP
Prints help information about this command.
.LP
.LP
\f4\-V \-\-version\fP
.LP
.LP
Prints version information about this command.
.LP
.LP
\f4\-J\fP\f2option\fP
.LP
.LP
Passes \f2option\fP to the Java launcher called by \f2pack200\fP. For example, \f2\-J\-Xms48m\fP sets the startup memory to 48 megabytes. Although it does not begin with \f2\-X\fP, it is not a standard option of \f2pack200\fP. It is a common convention for \f2\-J\fP to pass options to the underlying VM executing applications written in Java.
.LP
.SH "EXIT STATUS"
.LP
.LP
The following exit values are returned:
.LP
.LP
\f2\ 0\fP for successful completion;
.LP
.LP
\f2>0\fP if an error occurs.
.LP
.SH "SEE ALSO"
.LP
.RS 3
.TP 2
o
unpack200(1)
.TP 2
o
.na
\f2Java SE Documentation\fP @
.fi
http://docs.oracle.com/javase/7/docs/index.html
.TP 2
o
.na
\f2Java Deployment Guide \- Pack200\fP @
.fi
http://docs.oracle.com/javase/7/docs/technotes/guides/deployment/deployment\-guide/pack200.html
.TP 2
o
jar(1) \- Java Archive Tool
.TP 2
o
jarsigner(1) \- JAR Signer tool
.TP 2
o
\f2attributes(5)\fP man page
.RE
.LP
.SH "NOTES"
.LP
.LP
This command should not be confused with \f2pack(1)\fP. They are distinctly separate products.
.LP
.LP
The Java SE API Specification provided with the JDK is the superseding authority, in case of discrepancies.
.LP

85
desktop/test-osx/Tick's Tales.app/Contents/MacOS/jre/man/man1/policytool.1 Normal file
View File

@@ -0,0 +1,85 @@
." Copyright (c) 2001, 2011, Oracle and/or its affiliates. All rights reserved.
."
.TH policytool 1 "18 Jul 2013"
.LP
.SH "Name"
policytool \- PolicyTool Administration GUI Utility
.LP
\f3policytool\fP reads and writes a plain text policy file based on user input via the utility GUI.
.SH "SYNOPSIS"
.LP
.LP
Run the policytool Administrator's utility
.LP
.LP
\f4policytool\fP
.LP
.LP
Run policytool and load the specified policy file
.LP
.LP
\f4policytool\fP\f2[\-file\ \fP\f2filename\fP\f2]\fP
.LP
.LP
where:
.LP
.RS 3
.TP 3
file
directs \f2policytool\fP to load a local policy file
.TP 3
filename
The file name
.RE
.LP
.SH "DESCRIPTION"
.LP
.LP
\f3policytool\fP is a GUI that allows users to create and manage policy files. For details, see
.na
\f2the Policytool Users Guide\fP @
.fi
http://docs.oracle.com/javase/7/docs/technotes/guides/security/PolicyGuide.html.
.LP
.SH "OPTIONS"
.LP
.RS 3
.TP 3
file
Loads \f2filename\fP.
.RE
.LP
.SH "SEE ALSO"
.LP
.na
\f2Default Policy Implementation and Syntax\fP @
.fi
http://docs.oracle.com/javase/7/docs/technotes/guides/security/PolicyFiles.html
.br
.LP
.na
\f2Policy Tool Users' Guide\fP @
.fi
http://docs.oracle.com/javase/7/docs/technotes/guides/security/PolicyGuide.html
.br
.LP
.na
\f2Security Permissions\fP @
.fi
http://docs.oracle.com/javase/7/docs/technotes/guides/security/permissions.html
.br
.LP
.na
\f2Security Overview\fP @
.fi
http://docs.oracle.com/javase/7/docs/technotes/guides/security/overview/jsoverview.html
.br
.LP

309
desktop/test-osx/Tick's Tales.app/Contents/MacOS/jre/man/man1/rmid.1 Normal file
View File

@@ -0,0 +1,309 @@
." Copyright (c) 1998, 2011, Oracle and/or its affiliates. All rights reserved.
."
.TH rmid 1 "18 Jul 2013"
.LP
.SH "Name"
rmid \- The Java RMI Activation System Daemon
.LP
.LP
\f3rmid\fP starts the activation system daemon that allows objects to be registered and activated in a virtual machine (VM).
.LP
.SH "SYNOPSIS"
.LP
.nf
\f3
.fl
rmid [options]
.fl
\fP
.fi
.LP
.SH "DESCRIPTION"
.LP
.LP
The \f3rmid\fP tool starts the activation system daemon. The activation system daemon must be started before activatable objects can be either registered with the activation system or activated in a VM. See the
.na
\f2Java RMI Specification\fP @
.fi
http://docs.oracle.com/javase/7/docs/platform/rmi/spec/rmiTOC.html and
.na
\f2Activation tutorials\fP @
.fi
http://docs.oracle.com/javase/7/docs/technotes/guides/rmi/activation/overview.html for details on how to write programs that use activatable remote objects.
.LP
.LP
The daemon can be started by executing the \f2rmid\fP command, and specifying a security policy file, as follows:
.LP
.nf
\f3
.fl
rmid \-J\-Djava.security.policy=rmid.policy
.fl
\fP
.fi
.LP
.LP
\f3Note:\fP When running Sun's implementation of \f2rmid\fP, by default you will need to specify a security policy file so that \f2rmid\fP can verify whether or not the information in each \f2ActivationGroupDesc\fP is allowed to be used to launch a VM for an activation group. Specifically, the command and options specified by the \f2CommandEnvironment\fP and any \f2Properties\fP passed to an \f2ActivationGroupDesc\fP's constructor must now be explicitly allowed in the security policy file for \f2rmid\fP. The value of the \f2sun.rmi.activation.execPolicy\fP property dictates the policy that \f2rmid\fP uses to determine whether or not the information in an \f2ActivationGroupDesc\fP may be used to launch a VM for an activation group.
.LP
.LP
Executing \f2rmid\fP by default
.LP
.RS 3
.TP 2
o
starts the Activator and an internal registry on the default port, 1098, and
.TP 2
o
binds an \f2ActivationSystem\fP to the name \f2java.rmi.activation.ActivationSystem\fP in this internal registry.
.RE
.LP
.LP
To specify an alternate port for the registry, you must specify the \f2\-port\fP option when starting up \f2rmid\fP. For example,
.LP
.nf
\f3
.fl
rmid \-J\-Djava.security.policy=rmid.policy \-port 1099
.fl
\fP
.fi
.LP
.LP
starts the activation system daemon and a registry on the registry's default port, 1099.
.LP
.SS
Starting rmid from inetd/xinetd
.LP
.LP
An alternative to starting \f2rmid\fP from the command line is to configure \f2inetd\fP (Solaris) or \f2xinetd\fP (Linux) to start \f2rmid\fP on demand.
.LP
.LP
When \f2rmid\fP starts up, it attempts to obtain an inherited channel (inherited from \f2inetd\fP/\f2xinetd\fP) by invoking the \f2System.inheritedChannel\fP method. If the inherited channel is \f2null\fP or not an instance of \f2java.nio.channels.ServerSocketChannel\fP, then \f2rmid\fP assumes that it was not started by \f2inetd\fP/\f2xinetd\fP, and it starts up as described above.
.LP
.LP
If the inherited channel is a \f2ServerSocketChannel\fP instance, then \f2rmid\fP uses the \f2java.net.ServerSocket\fP obtained from the \f2ServerSocketChannel\fP as the server socket that accepts requests for the remote objects it exports, namely the registry in which the \f2java.rmi.activation.ActivationSystem\fP is bound and the \f2java.rmi.activation.Activator\fP remote object. In this mode, \f2rmid\fP behaves the same as when it is started from the command line, \f2except\fP:
.LP
.RS 3
.TP 2
o
Output printed to \f2System.err\fP is redirected to a file. This file is located in the directory specified by the \f2java.io.tmpdir\fP system property (typically \f2/var/tmp\fP or \f2/tmp\fP) with the prefix \f2"rmid\-err"\fP and the suffix \f2"tmp"\fP.
.TP 2
o
The \f2\-port\fP option is disallowed. If this option is specified, \f2rmid\fP will exit with an error message.
.TP 2
o
The \f2\-log\fP option is required. If this option is not specified, \f2rmid\fP will exit with an error message.
.RE
.LP
.LP
See the man pages for \f2inetd\fP (Solaris) or \f2xinetd\fP (Linux) for details on how to configure services to be started on demand.
.LP
.SH "OPTIONS"
.LP
.RS 3
.TP 3
\-C<someCommandLineOption>
Specifies an option that is passed as a command\-line argument to each child process (activation group) of \f2rmid\fP when that process is created. For example, you could pass a property to each virtual machine spawned by the activation system daemon:
.nf
\f3
.fl
rmid \-C\-Dsome.property=value
.fl
\fP
.fi
This ability to pass command\-line arguments to child processes can be useful for debugging. For example, the following command:
.nf
\f3
.fl
rmid \-C\-Djava.rmi.server.logCalls=true
.fl
\fP
.fi
will enable server\-call logging in all child VMs.
.LP
.TP 3
\-J<someCommandLineOption>
Specifies an option that is passed to the \f2java\fP interpreter running \f2rmid\fP. For example, to specify that \f2rmid\fP use a policy file named \f2rmid.policy\fP, the \f2\-J\fP option can be used to define the \f2java.security.policy\fP property on \f2rmid\fP's command line, for example:
.nf
\f3
.fl
rmid \-J\-Djava.security.policy=rmid.policy
.fl
\fP
.fi
.TP 3
\-J\-Dsun.rmi.activation.execPolicy=<policy>
Specifies the policy that \f2rmid\fP employs to check commands and command\-line options used to launch the VM in which an activation group runs. Please note that this option exists only in Sun's implementation of the Java RMI activation daemon. If this property is not specified on the command line, the result is the same as if \f2\-J\-Dsun.rmi.activation.execPolicy=default\fP were specified. The possible values of \f2<policy>\fP can be \f2default\fP, \f2<policyClassName>\fP, or \f2none\fP:
.RS 3
.TP 2
o
\f3default (or if this property is \fP\f4unspecified\fP\f3)\fP
.LP
The default \f2execPolicy\fP allows \f2rmid\fP to execute commands with specific command\-line options only if \f2rmid\fP has been granted permission to execute those commands and options in the security policy file that \f2rmid\fP uses. Only the default activation group implementation can be used with the \f2default\fP execution policy.
.LP
\f2rmid\fP launches a VM for an activation group using the information in the group's registered activation group descriptor, an \f2ActivationGroupDesc\fP. The group descriptor specifies an optional \f2ActivationGroupDesc.CommandEnvironment\fP which includes the \f2command\fP to execute to start the activation group as well as any command line \f2options\fP to be added to the command line. By default, \f2rmid\fP uses the \f2java\fP command found in \f2java.home\fP. The group descriptor also contains \f2properties\fP overrides that are added to the command line as options defined as:
.nf
\f3
.fl
\-D\fP\f4<property>\fP\f3=\fP\f4<value>\fP\f3
.fl
\fP
.fi
.LP
The permission \f2com.sun.rmi.rmid.ExecPermission\fP is used to grant \f2rmid\fP permission to execute a command, specified in the group descriptor's \f2CommandEnvironment\fP to launch an activation group. The permission \f2com.sun.rmi.rmid.ExecOptionPermission\fP is used to allow \f2rmid\fP to use command\-line options, specified as properties overrides in the group descriptor or as options in the \f2CommandEnvironment\fP, when launching the activation group.
.LP
When granting \f2rmid\fP permission to execute various commands and options, the permissions \f2ExecPermission\fP and \f2ExecOptionPermission\fP need to be granted universally (i.e., granted to all code sources).
.RS 3
.TP 3
ExecPermission
The \f2ExecPermission\fP class represents permission for \f2rmid\fP to execute a specific \f2command\fP to launch an activation group.
.LP
\f3Syntax\fP
.br
The \f2name\fP of an \f2ExecPermission\fP is the path name of a command to grant \f2rmid\fP permission to execute. A path name that ends in "/*" indicates all the files contained in that directory (where "/" is the file\-separator character, \f2File.separatorChar\fP). A path name that ends with "/\-" indicates all files and subdirectories contained in that directory (recursively). A path name consisting of the special token "<<ALL FILES>>" matches \f3any\fP file.
.LP
\f3Note:\fP A path name consisting of a single "*" indicates all the files in the current directory, while a path name consisting of a single "\-" indicates all the files in the current directory and (recursively) all files and subdirectories contained in the current directory.
.TP 3
ExecOptionPermission
The \f2ExecOptionPermission\fP class represents permission for \f2rmid\fP to use a specific command\-line \f2option\fP when launching an activation group. The \f2name\fP of an \f2ExecOptionPermission\fP is the value of a command line option.
.LP
\f3Syntax\fP
.br
Options support a limited wildcard scheme. An asterisk signifies a wildcard match, and it may appear as the option name itself (i.e., it matches any option), or an asterisk may appear at the end of the option name only if the asterisk follows either a "." or "=".
.LP
For example: "*" or "\-Dfoo.*" or "\-Da.b.c=*" is valid, "*foo" or "\-Da*b" or "ab*" is not.
.TP 3
Policy file for rmid
When granting \f2rmid\fP permission to execute various commands and options, the permissions \f2ExecPermission\fP and \f2ExecOptionPermission\fP need to be granted universally (i.e., granted to all code sources). It is safe to grant these permissions universally because only \f2rmid\fP checks these permissions.
.LP
An example policy file that grants various execute permissions to \f2rmid\fP is:
.nf
\f3
.fl
grant {
.fl
permission com.sun.rmi.rmid.ExecPermission
.fl
"/files/apps/java/jdk1.7.0/solaris/bin/java";
.fl
.fl
permission com.sun.rmi.rmid.ExecPermission
.fl
"/files/apps/rmidcmds/*";
.fl
.fl
permission com.sun.rmi.rmid.ExecOptionPermission
.fl
"\-Djava.security.policy=/files/policies/group.policy";
.fl
.fl
permission com.sun.rmi.rmid.ExecOptionPermission
.fl
"\-Djava.security.debug=*";
.fl
.fl
permission com.sun.rmi.rmid.ExecOptionPermission
.fl
"\-Dsun.rmi.*";
.fl
};
.fl
\fP
.fi
The first permission granted allow \f2rmid\fP to execute the 1.7.0 version of the \f2java\fP command, specified by its explicit path name. Note that by default, the version of the \f2java\fP command found in \f2java.home\fP is used (the same one that \f2rmid\fP uses), and does not need to be specified in the policy file. The second permission allows \f2rmid\fP to execute any command in the directory \f2/files/apps/rmidcmds\fP.
.LP
The third permission granted, an \f2ExecOptionPermission\fP, allows \f2rmid\fP to launch an activation group that defines the security policy file to be \f2/files/policies/group.policy\fP. The next permission allows the \f2java.security.debug\fP property to be used by an activation group. The last permission allows any property in the \f2sun.rmi\fP property name hierarchy to be used by activation groups.
.LP
To start \f2rmid\fP with a policy file, the \f2java.security.policy\fP property needs to be specified on \f2rmid\fP's command line, for example:
.LP
\f2rmid \-J\-Djava.security.policy=rmid.policy\fP
.RE
.TP 2
o
\f4<policyClassName>\fP
.LP
If the default behavior is not flexible enough, an administrator can provide, when starting \f2rmid\fP, the name of a class whose \f2checkExecCommand\fP method is executed in order to check commands to be executed by rmid.
.LP
The \f2policyClassName\fP specifies a public class with a public, no\-argument constructor and an implementation of the following \f2checkExecCommand\fP method:
.nf
\f3
.fl
public void checkExecCommand(ActivationGroupDesc desc,
.fl
String[] command)
.fl
throws SecurityException;
.fl
\fP
.fi
Before launching an activation group, \f2rmid\fP calls the policy's \f2checkExecCommand\fP method, passing it the activation group descriptor and an array containing the complete command to launch the activation group. If the \f2checkExecCommand\fP throws a \f2SecurityException\fP, \f2rmid\fP will not launch the activation group and an \f2ActivationException\fP will be thrown to the caller attempting to activate the object.
.TP 2
o
\f3none\fP
.LP
If the \f2sun.rmi.activation.execPolicy\fP property value is "none", then \f2rmid\fP will not perform any validation of commands to launch activation groups.
.RE
.LP
.TP 3
\-log dir
Specifies the name of the directory the activation system daemon uses to write its database and associated information. The log directory defaults to creating a directory, \f2log\fP, in the directory in which the \f2rmid\fP command was executed.
.LP
.TP 3
\-port port
Specifies the port \f2rmid\fP's registry uses. The activation system daemon binds the \f2ActivationSystem\fP, with the name \f2java.rmi.activation.ActivationSystem\fP, in this registry. Thus, the \f2ActivationSystem\fP on the local machine can be obtained using the following \f2Naming.lookup\fP method call:
.nf
\f3
.fl
import java.rmi.*;
.fl
import java.rmi.activation.*;
.fl
.fl
ActivationSystem system; system = (ActivationSystem)
.fl
Naming.lookup("//:\fP\f4port\fP/java.rmi.activation.ActivationSystem");
.fl
.fi
.TP 3
\-stop
Stops the current invocation of \f2rmid\fP, for a port specified by the \f2\-port\fP option. If no port is specified, it will stop the \f2rmid\fP running on port 1098.
.RE
.LP
.SH "ENVIRONMENT VARIABLES"
.LP
.RS 3
.TP 3
CLASSPATH
Used to provide the system a path to user\-defined classes. Directories are separated by colons. For example:
.nf
\f3
.fl
.:/usr/local/java/classes
.fl
\fP
.fi
.RE
.LP
.SH "SEE ALSO"
.LP
.LP
rmic(1),
.na
\f2CLASSPATH\fP @
.fi
http://docs.oracle.com/javase/7/docs/technotes/tools/index.html#classpath, java(1)
.LP

64
desktop/test-osx/Tick's Tales.app/Contents/MacOS/jre/man/man1/rmiregistry.1 Normal file
View File

@@ -0,0 +1,64 @@
." Copyright (c) 1997, 2011, Oracle and/or its affiliates. All rights reserved.
."
.TH rmiregistry 1 "18 Jul 2013"
.LP
.SH "Name"
rmiregistry \- The Java Remote Object Registry
.LP
.RS 3
The \f3rmiregistry\fP command starts a remote object registry on the specified port on the current host.
.RE
.LP
.SH "SYNOPSIS"
.LP
.nf
\f3
.fl
rmiregistry [\fP\f4port\fP\f3]
.fl
\fP
.fi
.LP
.SH "DESCRIPTION"
.LP
.LP
The \f3rmiregistry\fP command creates and starts a remote object registry on the specified \f2port\fP on the current host. If \f2port\fP is omitted, the registry is started on port 1099. The \f3rmiregistry\fP command produces no output and is typically run in the background. For example:
.LP
.LP
\f2rmiregistry &\fP
.LP
.LP
A remote object registry is a bootstrap naming service that is used by RMI servers on the same host to bind remote objects to names. Clients on local and remote hosts can then look up remote objects and make remote method invocations.
.LP
.LP
The registry is typically used to locate the first remote object on which an application needs to invoke methods. That object in turn will provide application\-specific support for finding other objects.
.LP
.LP
The methods of the \f2java.rmi.registry.LocateRegistry\fP class are used to get a registry operating on the local host or local host and port.
.LP
.LP
The URL\-based methods of the \f2java.rmi.Naming\fP class operate on a registry and can be used to look up a remote object on any host, and on the local host: bind a simple (string) name to a remote object, rebind a new name to a remote object (overriding the old binding), unbind a remote object, and list the URLs bound in the registry.
.LP
.SH "OPTIONS"
.LP
.RS 3
.TP 3
\-J
Used in conjunction with any \f2java\fP option, it passes the option following the \f2\-J\fP (no spaces between the \-J and the option) on to the \f2java\fP interpreter.
.RE
.LP
.SH "SEE ALSO"
.LP
java(1),
.na
\f2java.rmi.registry.LocateRegistry\fP @
.fi
http://docs.oracle.com/javase/7/docs/api/java/rmi/registry/LocateRegistry.html and
.na
\f2java.rmi.Naming\fP @
.fi
http://docs.oracle.com/javase/7/docs/api/java/rmi/Naming.html

94
desktop/test-osx/Tick's Tales.app/Contents/MacOS/jre/man/man1/servertool.1 Normal file
View File

@@ -0,0 +1,94 @@
." Copyright (c) 2001, 2011, Oracle and/or its affiliates. All rights reserved.
."
.TH servertool 1 "18 Jul 2013"
.LP
.SH "Name"
servertool \- The Java(TM) IDL Server Tool
.LP
\f3servertool\fP provides a command\-line interface for application programmers to register, unregister, startup, and shutdown a persistent server.
.SH "SYNOPSIS"
.LP
.nf
\f3
.fl
servertool \-ORBInitialPort \fP\f4nameserverport\fP\f3 \fP\f3options\fP\f3 [ \fP\f3commands\fP\f3 ]
.fl
\fP
.fi
.LP
.LP
If you did not enter a command when starting \f2servertool\fP, the command\-line tool displays with a \f2servertool >\fP prompt. Enter commands at the \f2servertool >\fP prompt.
.LP
.LP
If you enter a command when starting \f2servertool\fP, the Java IDL Server Tool starts, runs the command, and exits.
.LP
.LP
The \f2\-ORBInitialPort\fP \f2nameserverport\fP option is \f3required\fP. The value for \f2nameserverport\fP must specify the port on which \f2orbd\fP is running and listening for incoming requests. When using Solaris software, you must become root to start a process on a port under 1024. For this reason, we recommend that you use a port number greater than or equal to 1024 for the \f2nameserverport\fP.
.LP
.SH "DESCRIPTION"
.LP
.LP
The \f2servertool\fP provides the command\-line interface for the application programmers to register, unregister, startup, and shutdown a persistent server. Other commands are provided to obtain various statistical information about the server.
.LP
.SH "OPTIONS"
.LP
.RS 3
.TP 3
\-ORBInitialHost nameserverhost
Specifies the host machine on which the name server is running and listening for incoming requests. The \f2nameserverhost\fP defaults to \f2localhost\fP if this option is not specified. If \f2orbd\fP and \f2servertool\fP are running on different machines, you must specify the name or IP address of the host on which \f2orbd\fP is running.
.TP 3
\-Joption
Pass \f2option\fP to the Java virtual machine, where \f2option\fP is one of the options described on the reference page for java(1). For example, \f3\-J\-Xms48m\fP sets the startup memory to 48 megabytes. It is a common convention for \f3\-J\fP to pass options to the underlying virtual machine.
.RE
.LP
.SH "COMMANDS"
.LP
.RS 3
.TP 3
register \-server\ <server\ class\ name> \ \-classpath\ <classpath\ to\ server> [\ \-applicationName\ <application\ name> \-args\ <args\ to\ server> \-vmargs\ <flags\ to\ be\ passed\ to\ Java\ VM> \ ]
Register a new persistent server with the Object Request Broker Daemon (ORBD). If the server is not already registered, it is registered and activated. This command causes an install method to be invoked in the main class of the server identified by the \f2\-server\fP option. The install method must be \f2public static void install(org.omg.CORBA.ORB)\fP. The install method is optional and enables the developer to provide their own server installation behavior (for example, creating database schema).
.TP 3
unregister \-serverid\ <server\ id\ >\ | \-applicationName\ <application\ name>
Unregister a server from the ORBD by using either its server id or its application name. This command causes an uninstall method to be invoked in the main class of the server identified by the \f2\-server\fP option. The uninstall method must be \f2public static void uninstall(org.omg.CORBA.ORB)\fP. The uninstall method is optional and enables the developer to provide their own server uninstall behavior (for example, undoing the behavior of the install method).
.TP 3
getserverid \-applicationName\ <application\ name>
Return the server id that corresponds with an application.
.TP 3
list
List information about all persistent servers registered with the ORBD.
.TP 3
listappnames
List the application names for all servers currently registered with the ORBD.
.TP 3
listactive
List information about all persistent servers that have been launched by the ORBD and are currently running.
.TP 3
locate \-serverid\ <server\ id\ >\ | \-applicationName\ <application\ name> [\-endpointType\ <endpointType>\ ]
Locate the endpoints (ports) of a specific type for all ORBs created by a registered server. If a server is not already running, it is activated. If an endpoint type is not specified, then the plain/non\-protected endpoint associated with each ORB in a server is returned.
.TP 3
locateperorb \-serverid\ <server\ id\ >\ | \-applicationName\ <application\ name> [\-orbid\ <ORB\ name>\ ]
Locate all the endpoints (ports) registered by a specific ORB of registered server. If a server is not already running, then it is activated. If an \f2orbid\fP is not specified, the default value of "" is assigned to the \f2orbid\fP. If any ORBs are created with an \f2orbid\fP of empty string, all ports registered by it are returned.
.TP 3
orblist \-serverid\ <server\ id\ >\ | \-applicationName\ <application\ name>
Lists the ORBId of the ORBs defined on a server. An ORBId is the string name for the ORB created by the server. If the server is not already running, it is activated.
.TP 3
shutdown \-serverid\ <server\ id\ >\ | \-applicationName\ <application\ name>
Shutdown an active server that is registered with ORBD. During execution of this command, the \f2shutdown()\fP method defined in the class specified by either the \f2\-serverid\fP or \f2\-applicationName\fP parameter is also invoked to shutdown the server process appropriately.
.TP 3
startup \-serverid\ <server\ id\ >\ | \-applicationName\ <application\ name>
Startup or activate a server that is registered with ORBD. If the server is not running, this command launches the server. If the server is already running, an error message is returned to the user.
.TP 3
help
List all the commands available to the server through the server tool.
.TP 3
quit
Exit the server tool.
.RE
.LP
.SH "SEE ALSO"
.LP
orbd(1)

475
desktop/test-osx/Tick's Tales.app/Contents/MacOS/jre/man/man1/tnameserv.1 Normal file
View File

@@ -0,0 +1,475 @@
." Copyright (c) 1999, 2011, Oracle and/or its affiliates. All rights reserved.
."
.TH tnameserv 1 "18 Jul 2013"
.LP
.SH "Name"
Java IDL: Transient Naming Service \- \f2tnameserv\fP
.LP
.LP
This document discusses using the Java IDL Transient Naming Service, \f2tnameserv\fP. Java IDL also includes the Object Request Broker Daemon (ORBD). ORBD is a daemon process containing a Bootstrap Service, a Transient Naming Service, a \f3Persistent\fP Naming Service, and a Server Manager. The Java IDL tutorials all use ORBD, however, you can substitute \f2tnameserv\fP for \f2orbd\fP in any of the examples that use a Transient Naming Service. For documentation on the \f2orbd\fP tool, link to its orbd(1) or the
.na
\f2Java IDL Naming Service Included with ORBD\fP @
.fi
http://docs.oracle.com/javase/7/docs/technotes/guides/idl/jidlNaming.html topic.
.LP
.LP
Topics in this section include:
.LP
.RS 3
.TP 2
o
Java\ IDL Transient Naming Service
.TP 2
o
Starting the Java\ IDL Transient Naming Service
.TP 2
o
Stopping the Java\ IDL Transient Naming Service
.TP 2
o
Sample Client: Adding Objects to the Namespace
.TP 2
o
Sample Client: Browsing the Namespace
.RE
.LP
.SH "Java\ IDL Transient Naming Service"
.LP
.LP
The CORBA COS (Common Object Services) Naming Service provides a tree\-like directory for object references much like a filesystem provides a directory structure for files. The Transient Naming Service provided with Java IDL, \f2tnameserv\fP, is a simple implementation of the COS Naming Service specification.
.LP
.LP
Object references are stored in the namespace by name and each object reference\-name pair is called a name \f2binding\fP. Name bindings may be organized under \f2naming contexts\fP. Naming contexts are themselves name bindings and serve the same organizational function as a file system subdirectory. All bindings are stored under the \f2initial naming context\fP. The initial naming context is the only persistent binding in the namespace; the rest of the namespace is lost if the Java IDL naming service process halts and restarts.
.LP
.LP
For an applet or application to use COS naming, its ORB must know the port of a host running a naming service or have access to a stringified initial naming context for that naming service. The naming service can either be the Java\ IDL naming service or another COS\-compliant naming service.
.LP
.SH "Starting the Java\ IDL Transient Naming Service"
.LP
.LP
You must start the Java\ IDL naming service before an application or applet that uses its naming service. Installation of the Java\ IDL product creates a script (Solaris: \f2tnameserv\fP) or executable file (Windows NT: \f2tnameserv.exe\fP) that starts the Java\ IDL naming service. Start the naming service so it runs in the background.
.LP
.LP
If you do not specify otherwise, the Java\ IDL naming service listens on port 900 for the bootstrap protocol used to implement the ORB \f2resolve_initial_references()\fP and \f2list_initial_references()\fP methods, as follows:
.LP
.nf
\f3
.fl
tnameserv \-ORBInitialPort \fP\f4nameserverport\fP\f3&
.fl
\fP
.fi
.LP
.LP
If you do not specify the name server port, port 900 is used by default. When running Solaris software, you must become root to start a process on a port under 1024. For this reason, we recommend that you use a port number greater than or equal to 1024. To specify a different port, for example, 1050, and to run the naming service in the background, from a UNIX command shell, enter:
.LP
.nf
\f3
.fl
tnameserv \-ORBInitialPort 1050&
.fl
\fP
.fi
.LP
.LP
From an MS\-DOS system prompt (Windows), enter:
.LP
.nf
\f3
.fl
start tnameserv \-ORBInitialPort 1050
.fl
\fP
.fi
.LP
.LP
Clients of the name server must be made aware of the new port number. Do this by setting the \f2org.omg.CORBA.ORBInitialPort\fP property to the new port number when creating the ORB object.
.LP
.SS
Running the server and client on different hosts
.LP
.LP
In most of the Java IDL and RMI\-IIOP tutorials, the Naming Service, Server, and Client are all running on the development machine. In real world deployment, it is likely that the client and server will run on different host machines than the Naming Service.
.LP
.LP
For the client and server to find the Naming Service, they must be made aware of the port number and host on which the naming service is running. Do this by setting the \f2org.omg.CORBA.ORBInitialPort\fP and \f2org.omg.CORBA.ORBInitialHost\fP properties in the client and server files to the machine name and port number on which the Naming Service is running. An example of this is shown in
.na
\f2The Hello World Example Using RMI\-IIOP\fP @
.fi
http://docs.oracle.com/javase/7/docs/technotes/guides/rmi\-iiop/rmiiiopexample.html. You could also use the command line options \f2\-ORBInitialPort\fP \f2nameserverport#\fP and \f2\-ORBInitialHost\fP \f2nameserverhostname\fP to tell the client and server where to find the Naming Service.
.na
\f2Java IDL: Running the Hello World Example on TWO Machines\fP @
.fi
http://docs.oracle.com/javase/7/docs/technotes/guides/idl/tutorial/jidl2machines.html shows one way of doing this using the command line option.
.LP
.LP
For example, suppose the Transient Naming Service, \f2tnameserv\fP is running on port 1050 on host \f2nameserverhost\fP. The client is running on host \f2clienthost\fP and the server is running on host \f2serverhost\fP.
.LP
.RS 3
.TP 2
o
Start \f2tnameserv\fP on the host \f2nameserverhost\fP, as follows:
.nf
\f3
.fl
tnameserv \-ORBInitialPort 1050
.fl
.fl
\fP
.fi
.TP 2
o
Start the server on the \f2serverhost\fP, as follows:
.nf
\f3
.fl
java Server \-ORBInitialPort 1050 \-ORBInitialHost nameserverhost
.fl
\fP
.fi
.TP 2
o
Start the client on the \f2clienthost\fP, as follows:
.nf
\f3
.fl
java Client \-ORBInitialPort 1050 \-ORBInitialHost nameserverhost
.fl
\fP
.fi
.RE
.LP
.SS
The \-J option
.LP
This command\-line option is available for use with \f2tnameserve\fP:
.RS 3
.TP 3
\-Joption
Pass \f2option\fP to the Java virtual machine, where \f2option\fP is one of the options described on the reference page for java(1). For example, \f3\-J\-Xms48m\fP sets the startup memory to 48 megabytes. It is a common convention for \f3\-J\fP to pass options to the underlying virtual machine.
.RE
.LP
.SH "Stopping the Java\ IDL Transient Naming Service"
.LP
.LP
To stop the Java\ IDL naming service, use the relevant operating system command, such as \f2kill\fP for a Unix process, or \f2Ctrl\-C\fP for a Windows process. The naming service will continue to wait for invocations until it is explicitly shutdown. Note that names registered with the Java\ IDL naming service disappear when the service is terminated.
.LP
.SH "Sample Client: Adding Objects to the Namespace"
.LP
.LP
The following sample program illustrates how to add names to the namespace. It is a self\-contained Transient Naming Service client that creates the following simple tree.
.LP
.RS 3
.TP 2
o
\f4Initial Naming Context\fP
.RS 3
.TP 2
*
\f3plans\fP
.TP 2
*
\f4Personal\fP
.RS 3
.TP 2
-
\f3calendar\fP
.TP 2
-
\f3schedule\fP
.RE
.RE
.RE
.LP
.LP
In this example, \f3plans\fP is an object reference and \f3Personal\fP is a naming context that contains two object references: \f3calendar\fP and \f3schedule\fP.
.LP
.nf
\f3
.fl
import java.util.Properties;
.fl
import org.omg.CORBA.*;
.fl
import org.omg.CosNaming.*;
.fl
.fl
public class NameClient
.fl
{
.fl
public static void main(String args[])
.fl
{
.fl
try {
.fl
\fP
.fi
.LP
In the above section, Starting the Java IDL Transient Naming Service, the nameserver was started on port 1050. The following code ensures that the client program is aware of this port number.
.nf
\f3
.fl
Properties props = new Properties();
.fl
props.put("org.omg.CORBA.ORBInitialPort", "1050");
.fl
ORB orb = ORB.init(args, props);
.fl
.fl
\fP
.fi
.LP
This code obtains the initial naming context and assigns it to \f3ctx\fP. The second line copies \f3ctx\fP into a dummy object reference \f3objref\fP that we'll attach to various names and add into the namespace.
.nf
\f3
.fl
NamingContext ctx =
.fl
NamingContextHelper.narrow(orb.resolve_initial_references("NameService"));
.fl
NamingContext objref = ctx;
.fl
.fl
\fP
.fi
.LP
This code creates a name "plans" of type "text" and binds it to our dummy object reference. "plans" is then added under the initial naming context using \f2rebind\fP. The \f2rebind\fP method allows us to run this program over and over again without getting the exceptions we'd get from using \f2bind\fP.
.nf
\f3
.fl
NameComponent nc1 = new NameComponent("plans", "text");
.fl
NameComponent[] name1 = {nc1};
.fl
ctx.rebind(name1, objref);
.fl
System.out.println("plans rebind successful!");
.fl
.fl
\fP
.fi
.LP
This code creates a naming context called "Personal" of type "directory". The resulting object reference, \f3ctx2\fP, is bound to the name and added under the initial naming context.
.nf
\f3
.fl
NameComponent nc2 = new NameComponent("Personal", "directory");
.fl
NameComponent[] name2 = {nc2};
.fl
NamingContext ctx2 = ctx.bind_new_context(name2);
.fl
System.out.println("new naming context added..");
.fl
.fl
\fP
.fi
.LP
The remainder of the code binds the dummy object reference using the names "schedule" and "calendar" under the "Personal" naming context (\f3ctx2\fP).
.nf
\f3
.fl
NameComponent nc3 = new NameComponent("schedule", "text");
.fl
NameComponent[] name3 = {nc3};
.fl
ctx2.rebind(name3, objref);
.fl
System.out.println("schedule rebind successful!");
.fl
.fl
NameComponent nc4 = new NameComponent("calender", "text");
.fl
NameComponent[] name4 = {nc4};
.fl
ctx2.rebind(name4, objref);
.fl
System.out.println("calender rebind successful!");
.fl
.fl
.fl
} catch (Exception e) {
.fl
e.printStackTrace(System.err);
.fl
}
.fl
}
.fl
}
.fl
\fP
.fi
.LP
.SH "Sample Client: Browsing the Namespace"
.LP
.LP
The following sample program illustrates how to browse the namespace.
.LP
.nf
\f3
.fl
import java.util.Properties;
.fl
import org.omg.CORBA.*;
.fl
import org.omg.CosNaming.*;
.fl
.fl
public class NameClientList
.fl
{
.fl
public static void main(String args[])
.fl
{
.fl
try {
.fl
\fP
.fi
.LP
In the above section, Starting the Java IDL Transient Naming Service, the nameserver was started on port 1050. The following code ensures that the client program is aware of this port number.
.nf
\f3
.fl
.fl
Properties props = new Properties();
.fl
props.put("org.omg.CORBA.ORBInitialPort", "1050");
.fl
ORB orb = ORB.init(args, props);
.fl
.fl
.fl
\fP
.fi
.LP
The following code obtains the initial naming context.
.nf
\f3
.fl
NamingContext nc =
.fl
NamingContextHelper.narrow(orb.resolve_initial_references("NameService"));
.fl
.fl
\fP
.fi
.LP
The \f2list\fP method lists the bindings in the naming context. In this case, up to 1000 bindings from the initial naming context will be returned in the BindingListHolder; any remaining bindings are returned in the BindingIteratorHolder.
.nf
\f3
.fl
BindingListHolder bl = new BindingListHolder();
.fl
BindingIteratorHolder blIt= new BindingIteratorHolder();
.fl
nc.list(1000, bl, blIt);
.fl
.fl
\fP
.fi
.LP
This code gets the array of bindings out of the returned BindingListHolder. If there are no bindings, the program ends.
.nf
\f3
.fl
Binding bindings[] = bl.value;
.fl
if (bindings.length == 0) return;
.fl
.fl
\fP
.fi
.LP
The remainder of the code loops through the bindings and prints the names out.
.nf
\f3
.fl
for (int i=0; i < bindings.length; i++) {
.fl
.fl
// get the object reference for each binding
.fl
org.omg.CORBA.Object obj = nc.resolve(bindings[i].binding_name);
.fl
String objStr = orb.object_to_string(obj);
.fl
int lastIx = bindings[i].binding_name.length\-1;
.fl
.fl
// check to see if this is a naming context
.fl
if (bindings[i].binding_type == BindingType.ncontext) {
.fl
System.out.println( "Context: " +
.fl
bindings[i].binding_name[lastIx].id);
.fl
} else {
.fl
System.out.println("Object: " +
.fl
bindings[i].binding_name[lastIx].id);
.fl
}
.fl
}
.fl
.fl
} catch (Exception e) {
.fl
e.printStackTrace(System.err);
.fl
}
.fl
}
.fl
}
.fl
\fP
.fi
.LP

137
desktop/test-osx/Tick's Tales.app/Contents/MacOS/jre/man/man1/unpack200.1 Normal file
View File

@@ -0,0 +1,137 @@
." Copyright (c) 2004, 2011, Oracle and/or its affiliates. All rights reserved.
."
.TH unpack200 1 "18 Jul 2013"
.LP
.SH "Name"
unpack200 \- JAR Unpacking tool
.LP
.SH "SYNOPSIS"
.LP
.LP
\f4unpack200\fP\f2 [ \fP\f2options\fP ] \f2input\-file\fP \f2JAR\-file\fP
.LP
.LP
Options may be in any order. The last option on the command line supersedes all previously specified options.
.LP
.RS 3
.TP 3
input\-file
Name of the input file, which can be a pack200 gzip file or a pack200 file. The input could also be JAR file produced by pack200(1) with an effort of 0. In this case the contents of the input file will be copied to the output JAR file with the Pack200 marker.
.TP 3
JAR\-file
Name of the output JAR file.
.RE
.LP
.SH "DESCRIPTION"
.LP
.LP
\f2unpack200\fP is a native implementation that transforms a packed file produced by \f2pack200\fP(1) into a JAR file. Typical usage:
.LP
.LP
\f2% unpack200 myarchive.pack.gz myarchive.jar\fP
.LP
.LP
In this example, the \f2myarchive.jar\fP is produced from \f2myarchive.pack.gz\fP using the default \f2unpack200\fP settings.
.LP
.SH "OPTIONS"
.LP
.LP
\f4\-Hvalue \-\-deflate\-hint=\fP\f2value\fP
.LP
.LP
Sets the deflation to be \f2true\fP, \f2false\fP, or \f2keep\fP on all entries within a JAR file. The default mode is \f2keep\fP. If \f2true\fP or \f2false\fP, overrides the default behavior and sets the deflation mode on all entries within the output JAR file.
.LP
.LP
\f4\-r \-\-remove\-pack\-file\fP
.LP
.LP
Removes the input packed file.
.LP
.LP
\f4\-v \-\-verbose\fP
.LP
.LP
Outputs minimal messages. Multiple specification of this option will output more verbose messages.
.LP
.LP
\f4\-q \-\-quiet\fP
.LP
.LP
Specifies quiet operation with no messages.
.LP
.LP
\f4\-lfilename \-\-log\-file=\fP\f2filename\fP
.LP
.LP
Specifies a log file to output messages.
.LP
.LP
\f4\-? \-h \-\-help\fP
.LP
.LP
Prints help information about this command.
.LP
.LP
\f4\-V \-\-version\fP
.LP
.LP
Prints version information about this command.
.LP
.LP
\f4\-J\fP\f2option\fP
.LP
.LP
Passes \f2option\fP to the Java launcher called by \f2unpack200\fP.
.LP
.SH "EXIT STATUS"
.LP
.LP
The following exit values are returned:
.LP
.LP
\f2\ 0\fP if successful completion;
.LP
.LP
\f2>0\fP if an error occurred.
.LP
.SH "SEE ALSO"
.LP
.RS 3
.TP 2
o
pack200(1)
.TP 2
o
.na
\f2Java SE Documentation\fP @
.fi
http://docs.oracle.com/javase/7/docs/index.html
.TP 2
o
.na
\f2Java Deployment Guide \- Pack200\fP @
.fi
http://docs.oracle.com/javase/7/docs/technotes/guides/deployment/deployment\-guide/pack200.html
.TP 2
o
jar(1) \- Java Archive Tool
.TP 2
o
jarsigner(1) \- JAR Signer tool
.TP 2
o
\f2attributes(5)\fP man page
.RE
.LP
.SH "NOTES"
.LP
.LP
This command should not be confused with \f2unpack(1)\fP. They are distinctly separate products.
.LP
.LP
The Java SE API Specification provided with the JDK is the superseding authority, in case of discrepancies.
.LP