Missing home interface for bean '%BEAN_NAME%'

Missing remote interface for bean '%BEAN_NAME%'

When this is an EJB2 bean, the java class defined as remote interface of the bean has not been resolved

Missing primary key class for bean '%BEAN_NAME%''

No Home Interface for bean '%BEAN_NAME%' is registered in Knowledge Base

No Remote interface for bean '%BEAN_NAME%' is registered in Knowledge Base

No Bean class '%BEAN_NAME%' is registered in Knowledge Base

No Primary key class '%BEAN_NAME%' is registered in Knowledge Base

Duplicated %ELEMENT_DESCRIPTION% : '%ELEMENT_NAME%'

Duplicate declaration can be found in one of the follwing cases:

• More than one parameter type found when scanning, method or constructor declaration. Example, declare a type parameter <T> in a method itself declared in a class with a type parameter whose name is T
• Two fields with the same name
• In a method, constructor or lambda declaration, two variables or more have the same name.
• Two method declarations with same signature on the same context (class declaration for instance)
• Two types declaration/definitions with same name in same package.
• SQLJ variable has the same name as a field in the current scope

Most of these errors can be seen as ill-formed java code, and would require a change in the code for the warnings to disappear.

Files "%FILE1%" and "%FILE2%" have the same type. The first one will be used. Make sure you have choosen the right module directory.

You should configure the tld file with uri '%URI%' so that tags attributes values can be properly resolved.

Please update the file cast-tag.extensions.xml file with the uri '%URI%' so that tag attribute values can be properly resolved.

Unable to find file '%FILE_NAME%'

No persistence information files found using xml as search pattern

You should use uri '%URI%' to configure tags defined by tag files within sub-folder '%SUBFOLDER%' so that those tags attributes values can be properly resolved. Refer to online help on CAST tags extension mechanism.

Please update the tag files within the sub-folder '%SUBFOLDER%' with the uri '%URI%' so that the tag attribute values can be properly resolved. You can refer to the online help on CAST tags extension mechanism.

Syntax not  recognized

Unable to read file %CAUSE%

This warning is displayed if a file could not be read because it does not exist, is empty or if a file system error was encountered. The cause will be specified in the message.

Take action to resolve this warning based on the cause mentioned in the warning.

%CAUSE%

The persistence storage(table/view) '%TABLE_NAME%' could not be found among selected server objects.

Unable to process included file '%FILE%' (%MESSAGE%)

This included file may not have been delivered (missing in configuration) or there may be a mismatch in relative locations. If so, you need to check the delivered source code.

JAVA068: Duplicate %ELEMENT% declaration : %NAME%

The duplicate declaration should be corrected in the source code to avoid this warning

Custom tag '%NAME%' not found in tag library '%LIBRARY%' imported with prefix '%PREFIX%'

You should add the relevant taglib to resolve the warning. You can refer to the online help on CAST tags extension mechanism.

No taglib declaration found that uses '%PREFIX%' as prefix. Processing of all tags within file '%FILE%' that have that prefix may be incomplete

The taglib declaration is in the file that includes the other file. If this is the case, you can ignore this warning. First verify that this file is not included in another JSP file via a grep search.

The uri '%URI%' could not be resolved within the file web.xml or among the jar files deployed with your application

This error message appears when the TLD that contains the uri cannot be found. As consequence the TLD will not be managed, so if an attribute value with the same name as a database table is identified and this value also represents the name of a JSP Bean, an incorrect link will be created with the table and the JSP bean.

You should identify the TLD that is being used and add the associated *.tld or jar file to the analysis environment.

Class '%CLASS_NAME%' is not visible - one dependency is missing

The symbol would have been found without any warning where a dependency existed. As such, you need to check the dependency between the Analysis Unit or ignore the warning if there is no issue with the dependecy configuration.

Class '%CLASS_NAME%' not found in file as expected under classpath

To avoid this warning, you should either:

• find the source file in which this class is defined and then add the appropriate JAR to the class path
• or identify the framework in which the type is defined and select the appropriate Environment Profile

Unable to load %ELEMENT% '%NAME ( Unable to load class 'java.lang.Class" - Unable to load class 'java.lang.String" )

An attempt is made to resolve basic Java classes such as "java.lang.Class", "java.lang.Object", "java.lang.String" during an analysis. These classes are deliverered within the CAST AIP installation folder.

The error is reported when these classes are not found. In the vast majority of cases, the error occurs due to a corrupt installation of CAST AIP that revents the analyzer from resolving the classes.

Ensure that the CAST AIP installation folder is correct and that all expected files are present. In some cases, it may be necessary to re-install CAST AIP to resolve the error.

Please make sure that classpath includes core API libraries.

No parametrization trigger found for %METHOD_NAME%

A method '%METHOD_NAME%' has been found by the analyzer in Java code specified in your Analysis Unit and and it's not triggering an existing Parametrization rule from the selected Environment Profiles. Consequence: The method's arguments will be sent to a grep mechanism in order to create all possible links. Some of these links could be false links that may need to be ignored by the user through the Dynamic Link Manager.

You should create a custom Environment Profile in order to define Method Parametrization so that the analyzer can correctly identify links that are defined via custom methods. This will allow you to control the behavior of the JEE analyzer in order to match your custom dynamic programming methods. The Parametrization enables you to tell the JEE analyzer about your custom object creation methods so that it can correctly detect all dynamic and late binding calls automatically.

Cannot resolve '%NAME%' as %TYPE%%IN%%FROM%

As consequence of the missing components, some artifacts will not be present in the Analysis Service schema and so metrics and rules based on these artifacts will be impacted. To avoid this issue, you need to identify which library contains the unresolved component and add it in a new Environment Profile (when it is shared by several Applications) or through the class path in the archive list. The dependencies of Analysis Units should be also validated.

The target type used for the resolution of the parametrized trigger named "%METHOD_NAME%" is not supported.

Annotation '%ANNOTATION_NAME%' is not managed in Environment Profiles

The annotation whose fully qualified name is ANNOTATION_NAME, is not defined in any Environment Profiles used in the analysis (selected in the Analysis Unit or in the Application).

If this annotation is referenced in an existing Environment Profile, then you need to select it. In other cases (for instance for frameworks not yet supported by CAST AIP), you can make a custom Environment Profiles to handle annotation or ignore them: when this annotation is meaningless, you can ignore it or if it has a meaning, you will need to update an Environment Profile to handle it.

The classes of archive 'C:\ProgramData\CAST\CAST\Extensions\<JEE_EXTENSION>\EnvProf\J2EE\XXX.jar' are compiled with a different version of JSE than the version specified in this Job. This may lead to incorrect results or syntax error

The JSE version specified in this analysis configuration does not match the version used for the Jar Compilation. This may lead to incorrect results or syntax error (skipped files).

You should review the analysis configuration and specify the correct JSE version used by your Application. Otherwise, some files will be ignored and skipped during the analysis.

Info

This is an informational message about type resolution.