Example of such quality rules are
• Avoid many-to-many association.
• Avoid using references to the id in the persistent class's method equals()
• Persistent class method's equals() and hashCode() must access its fields through getter methods
• Persistent classes should Implement hashCode() and equals()
If any of the above quality rules are missing from the dashboard then the reason for this is hibernate profile not being selected in the CMS for analysis.
If you see that there are new quality rules in the current version of snapshot n and absent in snapshot n-1 though the source code has not changed and if the rules are related to Hibernate, then compare the previous analysis log with the current one to see if Hibernate profile is not selected in the previous analysis and is selected in the current analysis log which will explain the reason for this behaviour.
If you have used hibernate 3.3.2 or any higher version upto 4.0 in source code, but in CMS version 7.3.4 the last available hibernate version is 3.2 then you may select it for your analysis. The hibernate objects should be analyzed and the related quality rules should also be fired.
If you observe that hibernate diags are missing after installing a new service pack, the reason could be that you were using a custom hibernate profile before installing the Service pack. You deleted the associated file to the custom profile from the flat to be able to install the service pack, then you forgot to put the file back. Because the Hibernate file is missing, JPA entities are not created leading to missing diags in the dashboard.
To check this, go through J2EEE analysis log file, you should find a warning message like this:
Warning UNKNOWN ; Job execution Failed to analyze configuration file 'I:\LargeStorageArea2\LTSA\xxxx\Scr101\JavaTemp\Hibernate 4.0-4.3 JPA2\Hibernate 3.6-4.0 Annotations.xml'\n Queries files '<CASTflat>\EnvProf\J2EE\Hibernate\cast-hib-annotations-config-3.6-4.0.xml' not found. 0 ; 0 0 jspprse32\jsperrorhandler.cpp 567 JSPPrse32 0 0 jspprse32\jsperrorhandler.cpp
In the above message, the warning is there because the '<CASTflat>\EnvProf\J2EE\Hibernate\cast-hib-annotations-config-3.6-4.0.xml' file associated to the 'Hibernate 4.0-4.3 JPA2' customer environment profile is not in the flat directory.
To solve the issue, review your configuration to include properly the environment profile. Then rerun analysis to get the JPA entities created and getting the diag in your dashboard.