Java[tm] Application Verification Kit (AVK) for the Enterprise 5.0 Release Notes

 
 
Contents

Read This Section First

Users of Java Application Verification Kit (AVK) for the Enterprise should follow these steps:

  1. Install the software that Java AVK for the Enterprise relies on. See the Required Software section of this document.
  2. Read the Installation Instructions and install Java AVK for the Enterprise.
  3. Read the Java Application Verification Kit (AVK) for the Enterprise User's Guide to learn how to use the software.

Supported Platforms

Java AVK for the Enterprise is supported on the following platforms:

  • Sun Solaris 9 and 10 (SPARC), Solaris 9 and 10 (x86)
  • 64-bit Sun Solaris 10 (SPARC, x86)
  • Red Hat Enterprise Linux 3.0 Update 1 and 4.0
  • Windows 2000, Windows 2000 Advanced Server, Windows Server 2003, Windows XP Pro

New Features at This Release

At this release, Java AVK for the Enterprise has the following new features:

  • Java AVK for the Enterprise uses the call flow monitoring feature of Application Server 9 to perform dynamic verification.
  • The dynamic verification procedure has changed. In previous releases, you had to stop the Application Server in order to generate a verification report on an application. Now you perform the following steps while the Application Server is running:
    1. Deploy one or more applications.
    2. Start a dynamic verification session.
    3. Run your applications and generate one or more reports on them.
    4. When you have finished generating reports, end the dynamic verification session.

For details, read the Java Application Verification Kit (AVK) for the Enterprise User's Guide.

Removed Feature: Source Code Scanning

The SourceScan task, which was deprecated at the last release, has been removed at this release. The ArchiveTest task now does the work previously performed by this task.

What This Release Includes

This release of Java AVK for the Enterprise includes enhanced packages for Sun Java System Application Server Platform Edition 9 and a set of tools for performing the verification process.

Enhanced Packages for Sun Java System Application Server Platform Edition 9

The enhanced packages in Sun Java System Application Server Platform Edition 9 allow it to perform instrumentation and introspection at runtime on components based on the following specifications:

  • Enterprise JavaBeans (EJB)
  • Java Servlet API
  • JavaServer (JSP) Pages technology
  • JavaServer Faces API
  • Web Services for the Java EE platform

Tools

The tools provided with Java AVK for the Enterprise include a set of Ant tasks that allow you to do the following:

  • Scan code for proprietary APIs
  • Perform static archive testing to determine compatibility with the Java EE specifications
  • Translate runtime deployment descriptors

Required Software

The Java AVK for the Enterprise 5 release requires you to install version 5.0 Update 6 or higher of the Java Platform, Standard Edition Development Kit (JDK) on the systems where you will run Java AVK for the Enterprise.

The Java AVK for the Enterprise 5 release requires Sun Java System Application Server Platform Edition 9. The Java AVK for the Enterprise 5 release installation process can optionally install this software if you have not previously installed it.

Known Limitations

This release of Java AVK for the Enterprise has the following limitation:

  • The static verification tool may not report all errors in JSP pages the first time you run it on an application. If you fix the problems that are reported the first time you run the tool, additional problems may appear the next time you run the tool. If your application contains JSP pages, run the tool until it reports no errors.

Known Issues

Table 1 lists the known issues for this release of Java AVK for the Enterprise. Refer to the Sun Java System Application Server Platform Edition 9 Release Notes to find additional issues that may affect Java AVK for the Enterprise.

Table 1:   Known Issues for the Java AVK for the Enterprise 5 Release
Bug ID Description
4960017 On a Windows Server 2003 or Windows XP system, even if you have set the JAVA_HOME environment variable and placed the Java SE bin directory in your path, the self-installing executable for Java AVK for the Enterprise fails to find an existing JDK 5.0 installation. See the Installation Instructions for workarounds for this problem.
5002081 On certain versions of Linux, the installer may take several minutes to start. See the Installation Instructions for details.
5013031 Installation of Java AVK for the Enterprise may fail with an Existing Installation Detected error under under the following circumstances:
  • You previously installed a version of the Application Server while running as the root user or with Administrator privileges.
  • You moved or removed this version of the Application Server instead of uninstalling it.

See the Installation Instructions for workarounds for this problem.

5027028 To generate reports with correct results, you must run the static verification tests before you run the reporting tool. If you exercise the application and run the reporting tool before you run the static verification tests, you will see results for the runtime tests only. You must run the reporting tool again in order to join together the results from the static and runtime tests.
5030433 If the user chooses the registration option, but the installer cannot find a web browser from which to launch the registration page at the end of the installation, the installation exits silently. See the Installation Instructions for a workaround for this problem.
6203757 If you install Java AVK for the Enterprise on a Windows system and specify a previously installed version of the Application Server, the installation fails with an error message if you do not start the Application Server before you install Java AVK for the Enterprise.

Workaround: Use the Cancel button to stop the installation wizard. Then start the Application Server and run the installation wizard again.

6204876 If you run the TranslateRuntimeDD task against an application that calls the javax.naming.InitialContext constructor with a Hashtable argument, the task will modify the source code to use the no-argument form of the constructor. The TranslateRuntimeDD task places the modified code in the translated archive file, and you will have to replace the modified class file with the correct version.
6274161 During static archive testing, the EjbQLFromCmpEntityDescriptor test may fail for an EJB CMP archive with a description like the following: 
Error: Exception [ JDO74033: Cannot deploy application 'xxxx' module 
'xxxEjb' with CMP beans: cmp-resource is not defined for this module. 
The minimum requirement for a cmp-resource is to specify the jndi-name 
of a jdbc-resource or a persistence-manager-factory-resource to be used 
with the beans. ] while initializing JDO code generator

This error occurs if the file sun-cmp-mapping.xml is specified within the EJB bundle.

Workaround: Remove the sun-cmp-mapping.xml file from the EJB JAR file, recreate the archive, and then rerun the static-archive-test task.

6274968 The translate-dd task may fail with a message like the following: 
translate-dd:
    [delete] Deleting directory /opt/javke/reporttool/translate
     [java] May 24, 2005 11:19:56 AM com.sun.enterprise.appverification.tools.GenReportTool main
     [java] SEVERE: Could not create or parse document
     [echo] See "/opt/javke/reporttool/translate/translationSummary.html" for results.
     [echo] We attempted to create an ear file even if minor errors occurred
Workaround: Run this target more than once. Subsequent calls to this target execute successfully.
6297206 The report command and the static-archive-test task do not work if the Java AVK for the Enterprise installation path contains any spaces.

Workaround: Do not use spaces in the directory structure where you install Java AVK for the Enterprise. For example, avoid using directory names such as Program Files.

6416860

On a Windows system, the installer may crash if you run it on a system that has JDK 5.0 installed. See the Installation Instructions for a workaround for this problem.