The following document contains the results of PMD 6.13.0.
Rule | Violation | Line |
---|---|---|
ClassNamingConventions | The utility class name 'SuspiciousIdentityMapper' doesn't match '[A-Z][a-zA-Z0-9]+(Utils?|Helper|Home|Service)' | 46–76 |
Rule | Violation | Line |
---|---|---|
FormalParameterNamingConventions | The final method parameter name 'customer_id' doesn't match '[a-z][a-zA-Z0-9]*' | 226 |
Rule | Violation | Line |
---|---|---|
FieldNamingConventions | The constant name 'clientCode' doesn't match '[A-Z][A-Z_0-9]*' | 78 |
FieldNamingConventions | The constant name 'batchSize' doesn't match '[A-Z][A-Z_0-9]*' | 79 |
FieldNamingConventions | The constant name 'purgeSize' doesn't match '[A-Z][A-Z_0-9]*' | 80 |
FieldNamingConventions | The constant name 'limitationMode' doesn't match '[A-Z][A-Z_0-9]*' | 81 |
FieldNamingConventions | The constant name 'author' doesn't match '[A-Z][A-Z_0-9]*' | 84 |
Rule | Violation | Line |
---|---|---|
FieldNamingConventions | The field name 'nbIdentitiesMerged' doesn't match '_[a-z][a-zA-Z0-9]*' | 76 |
Rule | Violation | Line |
---|---|---|
FieldNamingConventions | The static field name 'instance' doesn't match '_[a-z][a-zA-Z0-9]*' | 49 |
FieldNamingConventions | The final field name '_duplicateServiceElasticSearch' doesn't match '[a-z][a-zA-Z0-9]*' | 50 |
Rule | Violation | Line |
---|---|---|
FieldNamingConventions | The final field name '_identityStoreNotifyListenerService' doesn't match '[a-z][a-zA-Z0-9]*' | 87 |
FieldNamingConventions | The final field name '_internalUserService' doesn't match '[a-z][a-zA-Z0-9]*' | 88 |
Rule | Violation | Line |
---|---|---|
FieldNamingConventions | The final field name '_nPriority' doesn't match '[a-z][a-zA-Z0-9]*' | 50 |
FormalParameterNamingConventions | The final method parameter name '_nPriority' doesn't match '[a-z][a-zA-Z0-9]*' | 58 |
Rule | Violation | Line |
---|---|---|
FieldNamingConventions | The final field name '_strRuleCode' doesn't match '[a-z][a-zA-Z0-9]*' | 49 |
FieldNamingConventions | The final field name '_strCustomerId' doesn't match '[a-z][a-zA-Z0-9]*' | 50 |
Rule | Violation | Line |
---|---|---|
FieldNamingConventions | The final field name '_request' doesn't match '[a-z][a-zA-Z0-9]*' | 55 |
Rule | Violation | Line |
---|---|---|
FieldNamingConventions | The final field name '_suspiciousIdentityExcludeRequest' doesn't match '[a-z][a-zA-Z0-9]*' | 48 |
Rule | Violation | Line |
---|---|---|
FieldNamingConventions | The final field name '_suspiciousIdentityChangeRequest' doesn't match '[a-z][a-zA-Z0-9]*' | 51 |
Rule | Violation | Line |
---|---|---|
FieldNamingConventions | The final field name '_suspiciousIdentityExcludeRequest' doesn't match '[a-z][a-zA-Z0-9]*' | 48 |
Rule | Violation | Line |
---|---|---|
FieldNamingConventions | The final field name '_request' doesn't match '[a-z][a-zA-Z0-9]*' | 48 |
Rule | Violation | Line |
---|---|---|
FieldNamingConventions | The final field name '_request' doesn't match '[a-z][a-zA-Z0-9]*' | 48 |
Rule | Violation | Line |
---|---|---|
CommentRequired | Enum comments are required | 5–25 |
Rule | Violation | Line |
---|---|---|
MissingBreakInSwitch | A switch statement does not contain a break | 62–71 |
AvoidCatchingGenericException | Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block | 98 |
Rule | Violation | Line |
---|---|---|
UseUtilityClass | All methods are static. Consider using a utility class instead. Alternatively, you could add a private constructor or make the class abstract to silence this warning. | 47–76 |
CommentRequired | Public method and constructor comments are required | 48–74 |
Rule | Violation | Line |
---|---|---|
ExcessiveImports | A high number of imports can indicate a high degree of coupling within an object. | 34–290 |
AvoidDuplicateLiterals | The String literal "Failure" appears 6 times in this file; the first occurrence is on line 103 | 103 |
AvoidDuplicateLiterals | The String literal "Conflict" appears 4 times in this file; the first occurrence is on line 104 | 104 |
UseObjectForClearerAPI | Rather than using a lot of String arguments, consider using a container object for those values. | 106–111 |
AvoidDuplicateLiterals | The String literal "Success" appears 4 times in this file; the first occurrence is on line 126 | 126 |
CommentRequired | Public method and constructor comments are required | 129–143 |
UseObjectForClearerAPI | Rather than using a lot of String arguments, consider using a container object for those values. | 129–135 |
AvoidDuplicateLiterals | The String literal "Request body" appears 4 times in this file; the first occurrence is on line 130 | 130 |
CommentRequired | Public method and constructor comments are required | 152–165 |
UseObjectForClearerAPI | Rather than using a lot of String arguments, consider using a container object for those values. | 152–157 |
CommentRequired | Public method and constructor comments are required | 174–188 |
UseObjectForClearerAPI | Rather than using a lot of String arguments, consider using a container object for those values. | 174–179 |
UseObjectForClearerAPI | Rather than using a lot of String arguments, consider using a container object for those values. | 203–207 |
UseObjectForClearerAPI | Rather than using a lot of String arguments, consider using a container object for those values. | 226–231 |
UseObjectForClearerAPI | Rather than using a lot of String arguments, consider using a container object for those values. | 252–256 |
CommentRequired | Public method and constructor comments are required | 275–288 |
UseObjectForClearerAPI | Rather than using a lot of String arguments, consider using a container object for those values. | 275–280 |
Rule | Violation | Line |
---|---|---|
CommentRequired | Header comments are required | 47–49 |
Rule | Violation | Line |
---|---|---|
ExcessiveImports | A high number of imports can indicate a high degree of coupling within an object. | 34–284 |
AvoidCatchingGenericException | Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block | 178 |
CyclomaticComplexity | The method 'processRule(DuplicateRule, int)' has a cyclomatic complexity of 15. | 184–257 |
ConfusingTernary | Avoid if (x != y) ..; else ..; | 205 |
AvoidDeeplyNestedIfStmts | Deeply nested if..then statements are hard to read | 219–223 |
AvoidCatchingGenericException | Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block | 248 |
Rule | Violation | Line |
---|---|---|
RedundantFieldInitializer | Avoid using redundant field initializer for 'nbIdentitiesMerged' | 76 |
ConfusingTernary | Avoid if (x != y) ..; else ..; | 93–151 |
AvoidLiteralsInIfCondition | Avoid using Literals in Conditional Statements | 112 |
Rule | Violation | Line |
---|---|---|
CommentRequired | Header comments are required | 47–74 |
AvoidFieldNameMatchingMethodName | Field instance has the same name as a method | 49 |
CommentRequired | Public method and constructor comments are required | 52–59 |
NonThreadSafeSingleton | Singleton is not thread safe | 54–57 |
CommentRequired | Public method and constructor comments are required | 61–67 |
CommentRequired | Public method and constructor comments are required | 69–73 |
Rule | Violation | Line |
---|---|---|
ExcessiveImports | A high number of imports can indicate a high degree of coupling within an object. | 34–358 |
CommentRequired | Header comments are required | 75–358 |
CommentRequired | Public method and constructor comments are required | 91–98 |
NonThreadSafeSingleton | Singleton is not thread safe | 93–96 |
ConfusingTernary | Avoid if (x != y) ..; else ..; | 127 |
UseConcurrentHashMap | If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation | 152 |
AvoidCatchingGenericException | Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block | 160 |
CommentRequired | Public method and constructor comments are required | 168–190 |
CommentRequired | Public method and constructor comments are required | 192–227 |
AvoidCatchingGenericException | Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block | 220 |
CommentRequired | Public method and constructor comments are required | 229–287 |
PrematureDeclaration | Avoid declaring a variable if it is unreferenced before a possible exit point. | 233 |
AvoidDuplicateLiterals | The String literal "Cannot find identity with cuid " appears 4 times in this file; the first occurrence is on line 237 | 237 |
UseConcurrentHashMap | If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation | 267 |
UseConcurrentHashMap | If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation | 273 |
AvoidCatchingGenericException | Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block | 281 |
CommentRequired | Public method and constructor comments are required | 289–346 |
PrematureDeclaration | Avoid declaring a variable if it is unreferenced before a possible exit point. | 293 |
UseConcurrentHashMap | If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation | 326 |
UseConcurrentHashMap | If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation | 332 |
AvoidCatchingGenericException | Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block | 340 |
CommentRequired | Public method and constructor comments are required | 348–351 |
CommentRequired | Public method and constructor comments are required | 353–357 |
Rule | Violation | Line |
---|---|---|
MissingSerialVersionUID | Classes implementing Serializable should set a serialVersionUID | 50–106 |
Rule | Violation | Line |
---|---|---|
ExcessiveImports | A high number of imports can indicate a high degree of coupling within an object. | 34–665 |
MissingSerialVersionUID | Classes implementing Serializable should set a serialVersionUID | 76–665 |
NullAssignment | Assigning an Object to null is a code smell. Consider refactoring. | 170 |
UnnecessaryAnnotationValueElement | Avoid the use of value in annotations when its the only element | 196 |
NullAssignment | Assigning an Object to null is a code smell. Consider refactoring. | 199 |
UseConcurrentHashMap | If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation | 209 |
UseDiamondOperator | Explicit type arguments can be replaced by Diamond Operator | 209 |
UseConcurrentHashMap | If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation | 242 |
ConfusingTernary | Avoid if (x != y) ..; else ..; | 259 |
UnnecessaryAnnotationValueElement | Avoid the use of value in annotations when its the only element | 269 |
NullAssignment | Assigning an Object to null is a code smell. Consider refactoring. | 272 |
UnnecessaryAnnotationValueElement | Avoid the use of value in annotations when its the only element | 340 |
UnnecessaryAnnotationValueElement | Avoid the use of value in annotations when its the only element | 363 |
PrematureDeclaration | Avoid declaring a variable if it is unreferenced before a possible exit point. | 456 |
UnnecessaryAnnotationValueElement | Avoid the use of value in annotations when its the only element | 483 |
NullAssignment | Assigning an Object to null is a code smell. Consider refactoring. | 486 |
ConfusingTernary | Avoid if (x != y) ..; else ..; | 519 |
Rule | Violation | Line |
---|---|---|
CommentRequired | Header comments are required | 48–88 |
UncommentedEmptyMethodBody | Document empty method body | 67–68 |
Rule | Violation | Line |
---|---|---|
CommentRequired | Header comments are required | 46–73 |
CommentRequired | Public method and constructor comments are required | 52–58 |
Rule | Violation | Line |
---|---|---|
CommentRequired | Header comments are required | 52–94 |
CommentRequired | Public method and constructor comments are required | 57–62 |
Rule | Violation | Line |
---|---|---|
CommentRequired | Header comments are required | 46–109 |
CommentRequired | Public method and constructor comments are required | 50–55 |
CyclomaticComplexity | The method 'doSpecificRequest()' has a cyclomatic complexity of 10. | 64–108 |
NullAssignment | Assigning an Object to null is a code smell. Consider refactoring. | 103 |
Rule | Violation | Line |
---|---|---|
UnusedImports | Avoid unused imports such as 'java.util.stream.Collectors' | 50 |
Rule | Violation | Priority | Line |
---|---|---|---|
CommentRequired | Enum comments are required | 3 | 5–25 |
Rule | Violation | Priority | Line |
---|---|---|---|
MissingBreakInSwitch | A switch statement does not contain a break | 3 | 62–71 |
AvoidCatchingGenericException | Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block | 3 | 98 |
Rule | Violation | Priority | Line |
---|---|---|---|
ClassNamingConventions | The utility class name 'SuspiciousIdentityMapper' doesn't match '[A-Z][a-zA-Z0-9]+(Utils?|Helper|Home|Service)' | 1 | 46–76 |
UseUtilityClass | All methods are static. Consider using a utility class instead. Alternatively, you could add a private constructor or make the class abstract to silence this warning. | 3 | 47–76 |
CommentRequired | Public method and constructor comments are required | 3 | 48–74 |
Rule | Violation | Priority | Line |
---|---|---|---|
ExcessiveImports | A high number of imports can indicate a high degree of coupling within an object. | 3 | 34–290 |
AvoidDuplicateLiterals | The String literal "Failure" appears 6 times in this file; the first occurrence is on line 103 | 3 | 103 |
AvoidDuplicateLiterals | The String literal "Conflict" appears 4 times in this file; the first occurrence is on line 104 | 3 | 104 |
UseObjectForClearerAPI | Rather than using a lot of String arguments, consider using a container object for those values. | 3 | 106–111 |
AvoidDuplicateLiterals | The String literal "Success" appears 4 times in this file; the first occurrence is on line 126 | 3 | 126 |
CommentRequired | Public method and constructor comments are required | 3 | 129–143 |
UseObjectForClearerAPI | Rather than using a lot of String arguments, consider using a container object for those values. | 3 | 129–135 |
AvoidDuplicateLiterals | The String literal "Request body" appears 4 times in this file; the first occurrence is on line 130 | 3 | 130 |
CommentRequired | Public method and constructor comments are required | 3 | 152–165 |
UseObjectForClearerAPI | Rather than using a lot of String arguments, consider using a container object for those values. | 3 | 152–157 |
CommentRequired | Public method and constructor comments are required | 3 | 174–188 |
UseObjectForClearerAPI | Rather than using a lot of String arguments, consider using a container object for those values. | 3 | 174–179 |
UseObjectForClearerAPI | Rather than using a lot of String arguments, consider using a container object for those values. | 3 | 203–207 |
UseObjectForClearerAPI | Rather than using a lot of String arguments, consider using a container object for those values. | 3 | 226–231 |
FormalParameterNamingConventions | The final method parameter name 'customer_id' doesn't match '[a-z][a-zA-Z0-9]*' | 1 | 226 |
UseObjectForClearerAPI | Rather than using a lot of String arguments, consider using a container object for those values. | 3 | 252–256 |
CommentRequired | Public method and constructor comments are required | 3 | 275–288 |
UseObjectForClearerAPI | Rather than using a lot of String arguments, consider using a container object for those values. | 3 | 275–280 |
Rule | Violation | Priority | Line |
---|---|---|---|
CommentRequired | Header comments are required | 3 | 47–49 |
Rule | Violation | Priority | Line |
---|---|---|---|
ExcessiveImports | A high number of imports can indicate a high degree of coupling within an object. | 3 | 34–284 |
FieldNamingConventions | The constant name 'clientCode' doesn't match '[A-Z][A-Z_0-9]*' | 1 | 78 |
FieldNamingConventions | The constant name 'batchSize' doesn't match '[A-Z][A-Z_0-9]*' | 1 | 79 |
FieldNamingConventions | The constant name 'purgeSize' doesn't match '[A-Z][A-Z_0-9]*' | 1 | 80 |
FieldNamingConventions | The constant name 'limitationMode' doesn't match '[A-Z][A-Z_0-9]*' | 1 | 81 |
FieldNamingConventions | The constant name 'author' doesn't match '[A-Z][A-Z_0-9]*' | 1 | 84 |
AvoidCatchingGenericException | Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block | 3 | 178 |
CyclomaticComplexity | The method 'processRule(DuplicateRule, int)' has a cyclomatic complexity of 15. | 3 | 184–257 |
ConfusingTernary | Avoid if (x != y) ..; else ..; | 3 | 205 |
AvoidDeeplyNestedIfStmts | Deeply nested if..then statements are hard to read | 3 | 219–223 |
AvoidCatchingGenericException | Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block | 3 | 248 |
Rule | Violation | Priority | Line |
---|---|---|---|
RedundantFieldInitializer | Avoid using redundant field initializer for 'nbIdentitiesMerged' | 3 | 76 |
FieldNamingConventions | The field name 'nbIdentitiesMerged' doesn't match '_[a-z][a-zA-Z0-9]*' | 1 | 76 |
ConfusingTernary | Avoid if (x != y) ..; else ..; | 3 | 93–151 |
AvoidLiteralsInIfCondition | Avoid using Literals in Conditional Statements | 3 | 112 |
Rule | Violation | Priority | Line |
---|---|---|---|
CommentRequired | Header comments are required | 3 | 47–74 |
AvoidFieldNameMatchingMethodName | Field instance has the same name as a method | 3 | 49 |
FieldNamingConventions | The static field name 'instance' doesn't match '_[a-z][a-zA-Z0-9]*' | 1 | 49 |
FieldNamingConventions | The final field name '_duplicateServiceElasticSearch' doesn't match '[a-z][a-zA-Z0-9]*' | 1 | 50 |
CommentRequired | Public method and constructor comments are required | 3 | 52–59 |
NonThreadSafeSingleton | Singleton is not thread safe | 3 | 54–57 |
CommentRequired | Public method and constructor comments are required | 3 | 61–67 |
CommentRequired | Public method and constructor comments are required | 3 | 69–73 |
Rule | Violation | Priority | Line |
---|---|---|---|
ExcessiveImports | A high number of imports can indicate a high degree of coupling within an object. | 3 | 34–358 |
CommentRequired | Header comments are required | 3 | 75–358 |
FieldNamingConventions | The final field name '_identityStoreNotifyListenerService' doesn't match '[a-z][a-zA-Z0-9]*' | 1 | 87 |
FieldNamingConventions | The final field name '_internalUserService' doesn't match '[a-z][a-zA-Z0-9]*' | 1 | 88 |
CommentRequired | Public method and constructor comments are required | 3 | 91–98 |
NonThreadSafeSingleton | Singleton is not thread safe | 3 | 93–96 |
ConfusingTernary | Avoid if (x != y) ..; else ..; | 3 | 127 |
UseConcurrentHashMap | If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation | 3 | 152 |
AvoidCatchingGenericException | Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block | 3 | 160 |
CommentRequired | Public method and constructor comments are required | 3 | 168–190 |
CommentRequired | Public method and constructor comments are required | 3 | 192–227 |
AvoidCatchingGenericException | Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block | 3 | 220 |
CommentRequired | Public method and constructor comments are required | 3 | 229–287 |
PrematureDeclaration | Avoid declaring a variable if it is unreferenced before a possible exit point. | 3 | 233 |
AvoidDuplicateLiterals | The String literal "Cannot find identity with cuid " appears 4 times in this file; the first occurrence is on line 237 | 3 | 237 |
UseConcurrentHashMap | If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation | 3 | 267 |
UseConcurrentHashMap | If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation | 3 | 273 |
AvoidCatchingGenericException | Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block | 3 | 281 |
CommentRequired | Public method and constructor comments are required | 3 | 289–346 |
PrematureDeclaration | Avoid declaring a variable if it is unreferenced before a possible exit point. | 3 | 293 |
UseConcurrentHashMap | If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation | 3 | 326 |
UseConcurrentHashMap | If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation | 3 | 332 |
AvoidCatchingGenericException | Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block | 3 | 340 |
CommentRequired | Public method and constructor comments are required | 3 | 348–351 |
CommentRequired | Public method and constructor comments are required | 3 | 353–357 |
Rule | Violation | Priority | Line |
---|---|---|---|
MissingSerialVersionUID | Classes implementing Serializable should set a serialVersionUID | 3 | 50–106 |
Rule | Violation | Priority | Line |
---|---|---|---|
ExcessiveImports | A high number of imports can indicate a high degree of coupling within an object. | 3 | 34–665 |
MissingSerialVersionUID | Classes implementing Serializable should set a serialVersionUID | 3 | 76–665 |
NullAssignment | Assigning an Object to null is a code smell. Consider refactoring. | 3 | 170 |
UnnecessaryAnnotationValueElement | Avoid the use of value in annotations when its the only element | 3 | 196 |
NullAssignment | Assigning an Object to null is a code smell. Consider refactoring. | 3 | 199 |
UseConcurrentHashMap | If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation | 3 | 209 |
UseDiamondOperator | Explicit type arguments can be replaced by Diamond Operator | 3 | 209 |
UseConcurrentHashMap | If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation | 3 | 242 |
ConfusingTernary | Avoid if (x != y) ..; else ..; | 3 | 259 |
UnnecessaryAnnotationValueElement | Avoid the use of value in annotations when its the only element | 3 | 269 |
NullAssignment | Assigning an Object to null is a code smell. Consider refactoring. | 3 | 272 |
UnnecessaryAnnotationValueElement | Avoid the use of value in annotations when its the only element | 3 | 340 |
UnnecessaryAnnotationValueElement | Avoid the use of value in annotations when its the only element | 3 | 363 |
PrematureDeclaration | Avoid declaring a variable if it is unreferenced before a possible exit point. | 3 | 456 |
UnnecessaryAnnotationValueElement | Avoid the use of value in annotations when its the only element | 3 | 483 |
NullAssignment | Assigning an Object to null is a code smell. Consider refactoring. | 3 | 486 |
ConfusingTernary | Avoid if (x != y) ..; else ..; | 3 | 519 |
Rule | Violation | Priority | Line |
---|---|---|---|
CommentRequired | Header comments are required | 3 | 48–88 |
FieldNamingConventions | The final field name '_nPriority' doesn't match '[a-z][a-zA-Z0-9]*' | 1 | 50 |
FormalParameterNamingConventions | The final method parameter name '_nPriority' doesn't match '[a-z][a-zA-Z0-9]*' | 1 | 58 |
UncommentedEmptyMethodBody | Document empty method body | 3 | 67–68 |
Rule | Violation | Priority | Line |
---|---|---|---|
CommentRequired | Header comments are required | 3 | 46–73 |
FieldNamingConventions | The final field name '_strRuleCode' doesn't match '[a-z][a-zA-Z0-9]*' | 1 | 49 |
FieldNamingConventions | The final field name '_strCustomerId' doesn't match '[a-z][a-zA-Z0-9]*' | 1 | 50 |
CommentRequired | Public method and constructor comments are required | 3 | 52–58 |
Rule | Violation | Priority | Line |
---|---|---|---|
UnusedImports | Avoid unused imports such as 'java.util.stream.Collectors' | 4 | 50 |
CommentRequired | Header comments are required | 3 | 52–94 |
FieldNamingConventions | The final field name '_request' doesn't match '[a-z][a-zA-Z0-9]*' | 1 | 55 |
CommentRequired | Public method and constructor comments are required | 3 | 57–62 |
Rule | Violation | Priority | Line |
---|---|---|---|
FieldNamingConventions | The final field name '_suspiciousIdentityExcludeRequest' doesn't match '[a-z][a-zA-Z0-9]*' | 1 | 48 |
Rule | Violation | Priority | Line |
---|---|---|---|
FieldNamingConventions | The final field name '_suspiciousIdentityChangeRequest' doesn't match '[a-z][a-zA-Z0-9]*' | 1 | 51 |
Rule | Violation | Priority | Line |
---|---|---|---|
FieldNamingConventions | The final field name '_suspiciousIdentityExcludeRequest' doesn't match '[a-z][a-zA-Z0-9]*' | 1 | 48 |
Rule | Violation | Priority | Line |
---|---|---|---|
FieldNamingConventions | The final field name '_request' doesn't match '[a-z][a-zA-Z0-9]*' | 1 | 48 |
Rule | Violation | Priority | Line |
---|---|---|---|
CommentRequired | Header comments are required | 3 | 46–109 |
FieldNamingConventions | The final field name '_request' doesn't match '[a-z][a-zA-Z0-9]*' | 1 | 48 |
CommentRequired | Public method and constructor comments are required | 3 | 50–55 |
CyclomaticComplexity | The method 'doSpecificRequest()' has a cyclomatic complexity of 10. | 3 | 64–108 |
NullAssignment | Assigning an Object to null is a code smell. Consider refactoring. | 3 | 103 |