Delivery Manager Tool - Package - Validation - Alerts - J2EE on Documentation - V2

Delivery Manager Tool - Package - Validation - Alerts - J2EE - Eclipse - Undefined variable

Mon, 01 Jan 0001 00:00:00 +0000

Description

This page explains how to solve the Undefined variable for J2EE Eclipse applications.

Observed in CAST AIP

Release	Yes/No
8.3.x	✅
8.2.x	✅
8.1.x	✅
8.0.x	✅
7.3.x	✅

Observed on RDBMS

RDBMS	Yes/No
Oracle Server	✅
Microsoft SQL Server	✅
CSS2	✅

Action Plan

In the package content tab, identify the path of the project. In the below example, the path is amisting/.project:
Go to the project path
Open the .classpath file
Inside the classpath file we can see that the variable that appears as undefined is defined in the classpath entry :
Search in your source where the jar files defined in the classpath entry are located (EXTERNAL_JARS/log_extract.jar as an example from the above screenshot).
Once found, in the package content remediate the undefined variable alert by giving the path of these jar files. In the current case the path is in R:/Sources/…/extlibs/src
Package again.
The undefined variable must not appear in the alerts again.
If the above steps do not help you, contact CAST Technical Support with the Relevant Input in order to reproduce the issue.

Notes/comments

Delivery Manager Tool - Package - Validation - Alerts - J2EE - Maven - Missing projects

Mon, 01 Jan 0001 00:00:00 +0000

Description

This page explains how to troubleshoot missing project alerts for J2EE applications.

Observed in CAST AIP

Release	Yes/No
8.3.x	✅
8.2.x	✅
8.1.x	✅
8.0.x	✅
7.3.x	✅

Observed on RDBMS

RDBMS	Yes/No
Oracle Server	✅
Microsoft SQL Server	✅
CSS2	✅

Action Plan

In the list of alerts “Missing projects”, if the Alerts are like [name1][name2] it means that the DMT has found a missing project (maven project or Eclipse project) which is refered by the poject file :

In the above example the project named rar/brcore is missing.
1. Open the project file of the file defined in the project path, in this example it is a maven project that is in : COMMON_CHECKOUT/trunk/sales-TKB/TKB-core/pom.xml. Check the reference to the project named rar/brcore.
2. Once the check is done, check if this project rar/brcore really exists in the packaged source code.
3. If it does not exist :
  1. Check if the missing project has been packaged in another package of the same version:
    1. If yes, you have to solve this alert with a manual remediation by pointing to the missing project and running the packaging.
    2. If no, then this alert is expected.
4. If it exists, to solve this alert you have to remediate manually this missing project alert
If the missing project alert is like [${variable}{project name}] as shown in the below screenshot, it means that a variable has not been resolved:
1. Check if this is an Undefined variable alert.
2. If yes, check that the variable which is not resolved is in the list of undefined variable alert.
3. If it is, remediate this undefined variable and package the source again.
4. If it is not, open the pom.xml file and replace the variable by its true value.
Check if the alerts are like [name1][name2]: as shown in the below screenshot :

In the above example, the project name is venibe-provider-cxf and it is refering to an artifact [org.apache.cxf][cxf-rt-transport-http]:3.0.3 which is missing. It is a jar file which is not found.
1. If there is no type of packaging listed in the pom.xml as in the screenshot below, then a jar file is expected for a dependency by default:
  1. if you have as well a pom type dependency in the pom.xml as in the screenshot below;
    
    Then this is an currently unsupported case as the type of dependency of pom type is currently not supported by CAST, though may be supported in a future release.
    1. As a manual workaround, gather all the associated jar files in the dependency lines of the pom.xml referenced in the alert, then add them in a file system package, and then finally add these jar files to the analysis unit’s class path so that they can be properly found.
2. Otherwise check if the missing jar exists in the source code packaged.
3. If it does not exist, getting this alert is expected
  1. You have to create a package : Automated extraction of required jar files which will point to a maven repository where the jar file exists.
  2. Run a package on the full version.
4. If it exists :
  1. Check if the version of the jar file is the correct one.
If the above steps do not help you, contact CAST Technical Support with the Relevant Input in order to reproduce the issue.

Relevant Input

Delivery Manager Tool - Relevant Input
Screenshot showing the alerts
In case of missing ressources / files / objects, provide a screenshot showing that these items exist.

Notes/comments

Delivery Manager Tool - Package - Validation - Alerts - J2EE - Maven - Missing source folder

Mon, 01 Jan 0001 00:00:00 +0000

Description

This page troubleshoots alerts related to missing source folder for Maven projects.

The standard directory layout for a Maven Project is shown below :

Application source code : src/main/java
Web application sources : src/main/webapp

In the pom.xml file, the sourceDirectory>

Observed in CAST AIP

Release	Yes/No
8.3.x	✅
8.2.x	✅
8.1.x	✅
8.0.x	✅
7.3.x	✅

Observed on RDBMS

RDBMS	Yes/No
Oracle Server	✅
Microsoft SQL Server	✅
CSS2	✅

Step by Step Scenario