Description

The first feature delivered in version 1.1 of the JEE analyzer is about simplifying analysis configuration. This is as part of the work already started in version1.0 and which will be continued in future versions.

Starting from version 1.1:

• you don't need to set the Struts version for your application as all supported versions (1.x and 2.x) will be activated by default and involved in the analysis if any Struts framework is used in the analyzed code.
• The efile objects for html and js files are no longer created starting from this version in order to avoid duplicate objects and duplicate/empty transactions (as similar objects are now created and handled by the HTML5 and JavaScript analyzer)
• This version also brings some improvement for analysis log readability. Some warnings regarding unsupported annotations/XML configuration files and method parametrizations are now displayed in debug mode only. This allows the user to focus on real and critical issues that need to be fixed to get more accurate analysis results. The transitions between analysis steps are now clearly defined in the log.

For more details about these features and resolved issues in the version, please check the content of what's new section below.

What's new?

See JEE Analyzer - 1.1 - Release Notes for more information.

Technology support

Language / Framework		Supported	Supported Versions
Java JDK			1.1 - 1.8
Presentation layer frameworks	Java Server Faces (JSF)		1.2 2.0, 2.1 This includes the support of the following third-party JSF libraries: Richfaces IceFaces MyFaces (Apache) PrimeFaces
	JSP		1.1, 1.2 2.0 Note: JSPX documents (JSP in XML format) are not supported. The HTML5 and JavaScript extension must be used to analyze JavaScript associated with the JSP.
	Apache Struts		1.0, 1.1 (including Tiles 1.0 and STXX 1.0 - 1.2) 2.0 - 2.5
	Struts Validator		1.2, 1.3
	STXX		1.0, 1.1, 1.2
Persistence layer frameworks	Hibernate		2.x 3.1, 3.2, 3.3, 3.4, 3.5, 3.6 4.0, 4.1, 4.2, 4.3-5.x
	JPA		1.0 2.0, 2.1
	EJB		2.0, 2.1 3.x (only @Stateless, @Stateful, @Local and @Remote annotations are supported)
Other frameworks	Spring IoC		1.2.x 2.x 3.x 4.x
	WSDL		1.1
	CDI		1.0, 1.1, 1.2
	Spring Batch		-

Function Point, Quality and Sizing support

This extension provides the following support:

• Function Points (transactions): a green tick indicates that OMG Function Point counting and Transaction Risk Index are supported
• Quality and Sizing: a green tick indicates that CAST can measure size and that a minimum set of Quality Rules exist

Function Points (transactions)	Quality and Sizing

CAST AIP compatibility

This extension is compatible with:

CAST AIP release	Supported
8.3.x
8.2.x
8.1.x
8.0.x
7.3.x

Supported DBMS servers

This extension is compatible with the following DBMS servers:

CAST AIP release	CSS	Oracle	Microsoft
All supported releases

Prerequisites

An installation of any compatible release of CAST AIP (see table above)

Required third-party software

The following section lists any third-party software that may be required to successfully deliver source code and run an analysis with the JEE Analyzer extension:

Dependencies with other extensions

Some CAST AIP extensions require the presence of other CAST AIP extensions in order to function correctly. The JEE Analyzer extension requires that the following other CAST AIP extensions are also installed:

• Web services linker service (internal technical extension)

Download and installation instructions

Please see:

• Download an extension
• Install an extension

Application qualification information

Please see: JEE - Application qualification specifics

Prepare and deliver the source code

Please see: JEE - Prepare and deliver the source code

Analysis configuration and execution

Please see: JEE - Analysis configuration and execution and all child pages:

• JEE - Analysis configuration
  • JEE - Analysis of pure Java applications
  • JEE - Framework analysis tips
    • EJB 3.x based application
    • JSF 1.2 based application
    • JSPX instead of JSP files
    • Spring based application
    • Struts 1.0 or 1.1 based application
    • Struts 2.0 and 2.1 based application
  • JEE - Handling action classes
  • JEE - Environment Profiles
    • JEE - JEE custom Environment Profiles
  • JEE - Advanced customization of a JEE analysis
    • Customize the cast-tag.extensions.xml
    • Manage annotations
    • Manage XML configuration files
      • FlexFramework - castscript Native Functions
      • FlexFramework - Description of the castscript language
      • FlexFramework - Hidden JEE Objects parent tree
      • JEE Analyzer - STXX support
    • Manage properties files
    • Manage JSP Tag Files
    • Manage JSP custom tags
• JEE - Run and validate analysis
  • JEE - Analysis messages
  • JEE - Analysis results

What analysis results can you expect?

Please see: JEE - Analysis results

Current known limitations

Quality Rules

Avoid static field of type collection (7562)

When calculating a snapshot for applications using JSE 5.0, the Quality Rule "Avoid static field of type collection (7562)" does not list as "Very High Risk Objects" classes that are or inherit from a Generic collection. The Quality Rule lists only the non generic form of collections. For example static attributes of type java.util.Collection<E> will not be reported as a violation.

Persistence: Avoid table and column names that are too long (portability) (7706)

Situation:

• JEE application using the Java Persistence API (JPA), e.g. in the form of Hibernate.
• A table or column name is not specified in the annotations of the JPA entity.

Symptoms: The JPA entity is not listed as a "Very High Risk" object in the results.

No link bookmarks generated

When Java Methods are defined inside a JSP file, no link bookmarks are generated (bookmarks can be seen in CAST Enlighten or in the Dynamic Link Manager). Example of a Java Method defined in a JSP file:

<%@ page language="Java" %> 
<%! 
public void myMethod(String message)
{ System.out.println(message); } 
%>