On this page:
Summary: This document provides information about changes and new features introduced in this release.
1.1.0-funcrel
Updates
JFAMILY-756 - Log improvements
Improvements have been made to the analysis log:
- some warnings are now only displayed in debug mode:
- XML file format not matching any env profile
- Annotation not managed
- No parametrization trigger found
- transitions between analysis steps are now clearly defined in the log.
Rule documentation improvements
The following improvements have been added to the rule documentation:
| Internal ID | Rule ID | Rule Name | Change implemented |
|---|---|---|---|
| JFAMILY-708 | 7728 | This rule has been tagged to state that it complies to "ASCRM-RLB-05: Runtime Resource Management Control Element in a Component Built to Run on Application Servers". | |
| JFAMILY-725 | 7150 | Favor PreparedStatement or CallableStatement over Statement | Rule description has been improved and enhanced. |
| JFAMILY-726 | 7730 | Use declarative transaction | Rule description has been improved and enhanced. |
| JFAMILY-725 | 7144 | Action Artifacts should not directly use database objects | Rule renamed to "Struts Action Artifacts should not directly use database objects". |
| JFAMILY-898 | 7146 | JSP pages should only reference Java Objects associated to J2EE Scoped Bean | Description has been updated to better explain the rule. |
Resolved issues
| Internal ID | Call ID | Description |
|---|---|---|
| JFAMILY-719 | - | Link is found "internally escalated" whereas expected normal link |
1.1.0-beta1
Resolved issues
| Internal ID | Call ID | Description |
|---|---|---|
| JFAMILY-667 | JEE052: Syntax not recognized | |
| JFAMILY-731 | 10672;12211 | The variable in lambda expression is not resolved |
| JFAMILY-732 | 12212 | Many warnings related to "can not resolve type or variable in lambda expression" |
| JFAMILY-733 | 11217 | JEE warning message 'can not resolve 'xxxx' as type or variable in lambda expression' |
| JFAMILY-752 | Incorrect and confusing naming for 22 new env profile files with extension.jar.blackbox.xml | |
| JFAMILY-759 | Performance Issue when parsing JSP files | |
| JFAMILY-768 | 12630 | False Violation for QR- Avoid double checked locking |
| JFAMILY-781 | 13363 | Java analysis completed with warning "Log the exception information: Unknown Exception..." |
| JFAMILY-793 | 11746 | Analysis failed with fatal error "unable to process JEE analysis |
| JFAMILY-794 | 11406 | False positive violation for the map and collect methods in QR-Avoid instantiations inside loops |
| JFAMILY-795 | 12743 | False Positive -- QR "Pages should use error handling page" |
| JFAMILY-796 | 11397 | Correction of QR description - Avoid using Fields (non static final) from other Classes- Missing violation |
| JFAMILY-797 | 12988 | New violations reported for QR : "Pages should use error handling page" for jsp files which are not changed |
| JFAMILY-798 | 11743 | Existing DLMs show up again as Un-reviewed post re-scan |
| JFAMILY-799 | 10484 | DLM highlighting special characters and partial strings |
| JFAMILY-800 | 11942 | Analysis fails with message"Unable to process JEE analysis, error in project" |
| JFAMILY-801 | 11516;12272 | False Violation for QR : Use lazy fetching for Collections |
| JFAMILY-810 | 13637 | Fatal error caught during JEE analysis of file listJobs.xhtml : Warning saying "Unknown Exception" |
| JFAMILY-812 | JEE LOC 0 post migration |
1.1.0-alpha1
New features
Default activation of all supported Struts versions for Java analysis
Since the release of the JEE Analyzer extension 1.0.0, all frameworks are activated by default and set to "latest" in the CAST Management Studio. In the JEE Analyzer extension 1.1, work has started to simplify this framework configuration process by activating support of the latest framework by default and not allowing the selection of a previous version of a framework in the CAST Management Studio.
In JEE Analyzer 1.1.0, the work has started with the Apache Struts framework:
- All supported versions of the Apache Struts framework are now configured in one single environment profile that is active by default.
- The corresponding "Struts" option in the CAST Management Studio will still exist, but changing the option will have no effect at all. The option will be removed in a future release of CAST AIP.
This work will continue in future releases of the JEE Analyzer.
eFile objects for html and js files are no longer created
The JEE analyzer will no longer create eFile objects for html and js files. This is to avoid the following situations:
- getting duplicate objects cause by the creation of identical objects by the HTML5/JavaScript extension.
- getting duplicate and empty transaction transactions.
Therefore, when upgrading to JEE Analyzer 1.1.0 and re-analyzing the same source code, you may find that your results change as follows:
- reduced number of objects (but no duplications), therefore more accurate.
- reduced number of empty and duplicate transactions, therefore more accurate.
Resolved issues
| Internal ID | Call ID | Summary |
|---|---|---|
| JFAMILY-696 |
| Activate Struts 1 and Struts 2 versions by default for JEE Analysis |
| JFAMILY-661 | [CASTONCAST] Transactions are incomplete because JEE Analyzer does not create links to "JPA Named Queries" | |
| JFAMILY-704 | Avoid calling finalize() documentation - new naming style | |
| JFAMILY-705 | QR Proper overriding of 'finalize()' documentation - new naming style | |
| JFAMILY-753 | Many occurrences of the warning JAVA131 and this message is not documented | |
| JFAMILY-704 | Avoid calling finalize() documentation - new naming style |
