Sponsored Content
Full Discussion: Code deployment issue
Special Forums Windows & DOS: Issues & Discussions Code deployment issue Post 302120874 by harimadhavbalu on Friday 8th of June 2007 09:39:22 PM
Old 06-08-2007
Yeah, Actually I found the reason for the error. The Unix environment needed more references from Apache SAX Parser. Some how it was not required when I developed in Eclipse. Thanks for your time and consideration.

Regards

Hari
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

What UNIX is best for an all-in-one-server deployment

Heya, my university department wants to deploy a UNIX based system instead of various unnetokred windows PCs. We are trying to build a terminal server solution on either FreeBSD,Solaris or Debian Linux. The system would mostly run office applications on X11 and file sharing (with Samba). In... (4 Replies)
Discussion started by: masterfreek64
4 Replies

2. Web Development

Looking for a tool for SVN deployment

Please help! I am looking for a tool which can perform following tasks: 1. Display repository lists 2. Upload repository via ssh to production server 3. Check the last repository number updated 4. Capable to work with Apache and PHP on Linux OS. Thank you. (2 Replies)
Discussion started by: greenja
2 Replies

3. Shell Programming and Scripting

Application Deployment Script

Dear All, I have been deploying my web application binary on Jboss application server manually on 13 servers with 2 instances on each server. i.e. 26 instances. It is really becoming time consuming to deploy the application manually. I am looking for a script which would deploy my binary file... (1 Reply)
Discussion started by: Siddheshk
1 Replies

4. Shell Programming and Scripting

Application Deployment Script

Hi, I need to develop a script which will deploy my web application binary(.war) file in the jboss application server. I also need to take the back up of the existing binary file and rename the same with current date and then deploy the new binary from my specified location. The same... (1 Reply)
Discussion started by: Siddheshk
1 Replies

5. UNIX for Advanced & Expert Users

Unattended disk image deployment?

Hi I need a system that allows a PC to PXE boot and then fully unattended deploy a diskimage created from a Linux system with identical hardware and then reboot when finished. I have been looking around but have not found a tool that is capable of doing this without too many bells and whistles,... (2 Replies)
Discussion started by: smith0083
2 Replies

6. Red Hat

war file deployment

Hi Experts. I need to install one help library in Fedora 13 and I got the installation document for it: --------------------------------------------------- users need their own J2EE web application server to be able to complete this installation. The server must support J2EE - JSP... (3 Replies)
Discussion started by: orma
3 Replies

7. Shell Programming and Scripting

Shell scripting for application deployment

hi all, i want script for this one 1. Download the zip from the ftp 2. Take backup of the current application 3. Deploy the zip in webapps Unzip the file. 4. Configure DB values. 5. Restart tomcat Thanks Advance, janny. (1 Reply)
Discussion started by: mohan999999
1 Replies

8. Solaris

Deployment of flar image into the global zone

Hi Folks, I know that we can install the flar image inside solaris non-global or branded zones. But can we install flar image in the global zone? If yes, then how? My use case is, while preparing setups, every time i needs to install Solaris OS (say sol10) on the machine and have to install... (1 Reply)
Discussion started by: Vaishey
1 Replies
GJARSIGNER(1)                                                           GNU                                                          GJARSIGNER(1)

NAME
gjarsigner - Java ARchive (JAR) file signing and verification tool SYNOPSIS
jarsigner [OPTION]... FILE ALIAS jarsigner -verify [OPTION]... FILE DESCRIPTION
When the first form is used, the tool signs the designated JAR file. The second form, on the other hand, is used to verify a previously signed JAR file. FILE is the .JAR file to process; i.e., to sign if the first syntax form is used, or to verify if the second syntax form is used instead. ALIAS must be a known Alias of a Key Entry in the designated Key Store. The private key material associated with this Alias is then used for signing the designated .JAR file. OPTIONS
Common options The following options may be used when the tool is used for either signing, or verifying, a .JAR file. -verbose Use this option to force the tool to generate more verbose messages, during its processing. -internalsf When present, the tool will include --which otherwise it does not-- the ".SF" file in the ".DSA" generated file. -sectionsonly When present, the tool will include in the ".SF" generated file --which otherwise it does not-- a header containing a hash of the whole manifest file. When that header is included, the tool can quickly check, during verification, if the hash (in the header) matches or not the manifest file. -provider PROVIDER_CLASS_NAME A fully qualified class name of a Security Provider to add to the current list of Security Providers already installed in the JVM in- use. If a provider class is specified with this option, and was successfully added to the runtime --i.e. it was not already installed-- then the tool will attempt to remove this Security Provider before exiting. -help Prints a help text similar to this one. Signing options The following options may be specified when using the tool for signing purposes. -keystore URL Use this option to specify the location of the key store to use. The default value is a file URL referencing the file named .keystore located in the path returned by the call to "java.lang.System#getProperty(String)" using "user.home" as argument. If a URL was specified, but was found to be malformed --e.g. missing protocol element-- the tool will attempt to use the URL value as a file-name (with absolute or relative path-name) of a key store --as if the protocol was "file:". -storetype STORE_TYPE Use this option to specify the type of the key store to use. The default value, if this option is omitted, is that of the property "keystore.type" in the security properties file, which is obtained by invoking the static method call "getDefaultType()" in "java.security.KeyStore". -storepass PASSWORD Use this option to specify the password which will be used to unlock the key store. If this option is missing, the User will be prompted to provide a password. -keypass PASSWORD Use this option to specify the password which the tool will use to unlock the Key Entry associated with the designated Alias. If this option is omitted, the tool will first attempt to unlock the Key Entry using the same password protecting the key store. If this fails, you will then be prompted to provide a password. -sigfile NAME Use this option to designate a literal that will be used to construct file names for both the ".SF" and ".DSA" signature files. These files will be generated, by the tool, and placed in the META-INF directory of the signed JAR. Permissible characters for NAME must be in the range "a-zA-Z0-9_-". All characters will be converted to upper-case ones. If this option is missing, the first eight characters of the ALIAS argument will be used. When this is the case, any character in ALIAS that is outside the permissible range of characters will be replaced by an underscore. -signedjar FILE Use this option to specify the file name of the signed JAR. If this option is omitted, then the signed JAR will be named the same as FILE; i.e., the input JAR file will be replaced with the signed copy. Verification options The following options may be specified when using the tool for verification purposes. -verify Use this option to indicate that the tool is to be used for verification purposes. -certs This option is used in conjunction with the -verbose option. When present, along with the -verbose option, the tool will print more detailed information about the certificates of the signer(s) being processed. BUGS
SEE ALSO
AUTHOR
0.98 2010-07-05 GJARSIGNER(1)
All times are GMT -4. The time now is 07:07 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy