EJBCA 3.8.1 (Development branch)


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News EJBCA 3.8.1 (Development branch)
# 1  
Old 01-29-2009
EJBCA 3.8.1 (Development branch)

Image EJBCA is a fully functional Certificate Authority in Java using J2EE technology. It builds on the J2EE platform to create a robust, high performance, platform independent, flexible, and component-based CA to be used standalone or integrated in any J2EE app. EJBCA comes with a flexible and powerful Web-based admin GUI. License: GNU Lesser General Public License (LGPL) Changes:
Broken support for Glassfish was fixed. Support for JBoss 5.0 was added. Support for Weblogic 10.3 was improved. IPv6 subject alternative names were fixed. A few minor bugs were fixed. Image

Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question
verifier(1M)                                                Application Server Utility                                                verifier(1M)

NAME
verifier - validates the J2EE Deployment Descriptors against application server DTDs SYNOPSIS
verifier [-v] [-d destination_directory] [-r [a|w|f]] jar_filename Use the verifier utility to validate the J2EE deployment descriptors and the Sun ONE Application Server specific deployment descriptors. If the application is not J2EE compliant, an error message is printed. When you run the verifier utility, two results files are created in XML and TXT format. The location where the files are created can be configured using the -d option. The directory specified as the destination directory for result files should exist. If no directory is specified, the result files are created in the current directory. Result files are named as jar_filename_verified.xml and jar_filename_ver- ified.txt The XML file has various sections that are dynamically generated depending on what kind of application or module is being verified. The root tag is static-verification which may contain the tags application, ejb, web, appclient, connector, other, error and failure-count. The tags are self explanatory and are present depending on the type of module being verified. For example, an EAR file containing a web and EJB module will contain the tags application, ejb, web, other, and failure-count. If the verifier ran successfully, a result code of 0 is returned. A non-zero error code is returned if the verifier failed to run. OPTIONS
-v verbose debugging is turned on. -d identifies where the result files get placed. -r identifies the reporting level defined as one of the following: o a sets output reporting level to display all results (default) o w sets output reporting level to display warning and failure results o f sets output reporting level to display only failure results jar_filename name of the ear/war/jar file to perform static verification on. The results of verification are placed in two files jar_filename_verified.xml and jar_filename_verified.txt in the destination directory. Example 1: Using verifier in the Verbose Mode example% verifier -v -d /verifier-results -rf sample.ear Where -v runs the verifier in verbose mode, -d specifies the destination directory, and -rf displays only the failures. The results are stored in /verifier-results/sample.ear_verified.xml and /verifier-results/sample.ear_verified.txt. asadmin(1M) Sun Java System Application Server March 2004 verifier(1M)