unpack200(1) [mojave man page]
unpack200(1) General Commands Manual unpack200(1) NAME
unpack200 - JAR Unpacking tool SYNOPSIS
unpack200 [ OPTIONS ] input-file JAR-file PARAMETERS
The options may be in any order. The last option on the command line supersedes all previously specified options. For a discussion of the options, see OPTIONS below. 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. JAR-file name of the output JAR file. DESCRIPTION
The unpack200 tool is a native implementation that transforms a packed file produced by pack200(1) into a JAR file. Typical usage: % unpack200 myarchive.pack.gz myarchive.jar In this example, the myarchive.jar is produced from myarchive.pack.gz using the default unpack200 settings. OPTIONS
-Hvalue --deflate-hint=value Sets the deflation to be true, false, or keep on all entries within a JAR file. The default mode is keep. If true or false, over- rides the default behavior and sets the deflation mode on all entries within the output JAR file. Non-Standard Options -r --remove-pack-file Removes the input packed-file. -v --verbose Outputs minimal messages, multiple specification of this option will output more verbose messages. -q --quiet Specifies quiet operation with no messages. -lfilename --log-file=filename Specifies a log file to output messages. EXIT STATUS
The following exit values are returned: 0 Successful completion. >0 An error occurred. SEE ALSO
pack200(1), jar(1), jarsigner(1), attributes(5) For API specification and other related information: http://java.sun.com/j2se/5.0/docs http://java.sun.com/j2se/5.0/docs/guide/deployment/deployment-guide/pack200.html NOTES
: This command should not be confused with unpack(1). They are distinctly separate products. The J2SE API Specification provided with the JDK release is the superseding authority, in case of discrepancies. 14 July 2004 unpack200(1)
Check Out this Related Man Page
appclient(1M) Application Server Utility appclient(1M) NAME
appclient - launches the Application Client Container and invokes the client application packaged in the application JAR file SYNOPSIS
appclient -client client_application_jar [-mainclass client_application_main_classname|-name display_name] [-xml sun-acc.xml file] [-tex- tauth] [-user username] [-password password] Use the appclient command to launch the application client container and invoke a client application that is packaged in an application JAR file. The application client jar file is psecified and created during deployment either by the deploytool or by using the asadmin deploy command. The application client container is a set of java classes, libraries and other files that are required to execute a first-tier application client program on a Java Virtual Machine (JVM). The application client container communicates with the Application Server using RMI-IIOP. The client.jar that is retrieved after deploying an application , should be passed with the -client option while running the appclient utility. The -mainclass and -name options are optional for a single client application. For multiple client applications use either the -classname option or the- name option. -client required; the name and location for the client application jar file. The application client JAR file is specified and created during deployment, either by the deploytool or by the asadmin deploy command. -mainclass optional; the full classname of the main client application main() method that will be invoked by the Application Client Container. Used for a single client application. By default, uses the class specified in the client jar. The class name must be the full name. For example, com.sun.test.AppClient -name optional; the display name for the client application. Used for multiple client applications. By default, the dis- play name is specified in the client jar application-client.xml file which is identified by the display-name attribute. -xml optional if using the default domain and instance, otherwise it is required; identifies the name and location of the client configuration XML file. If not specified, defaults to the value of $AS_ACC_CONFIG identified in asenv.conf file. -textauth optional; used to specify using text format authentication when authentication is needed. Example 1: Using the appclient command appclient -client appserv/bin/myclientapp.jar -mainclass com.sun.test.TestAppClient -xml sun-acc.xml scott sample Where: appserv/bin/myclientapp.jar is the full path for the client application .jar file, com.sun.text.TestAppClient is the full Java pack- age name of the main client application, scott and sample are arguments to pass to the application, and sun-acc.xml is the name of the client configuration XML file. If sun-acc.xml is not in the current directory, you must give the absolute path location; otherwise the rel- ative path is used. The relative path is relative to the directory where the command is being executed. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Interface Stability |Unstable | +-----------------------------+-----------------------------+ package-appclient(1M), asadmin(1M) Sun Java System Application Server March 2004 appclient(1M)