The following document contains the results of PMD 6.13.0.
| Rule | Violation | Line |
|---|---|---|
| ClassWithOnlyPrivateConstructorsShouldBeFinal | A class which only has private constructors should be final | 8–55 |
| ClassNamingConventions | The utility class name 'NotificationStoreConstants' doesn't match '[A-Z][a-zA-Z0-9]+(Utils?|Helper|Home|Service)' | 8–55 |
| Rule | Violation | Line |
|---|---|---|
| ClassWithOnlyPrivateConstructorsShouldBeFinal | A class which only has private constructors should be final | 47–91 |
| Rule | Violation | Line |
|---|---|---|
| LoggerIsNotStaticFinal | The Logger variable declaration does not contain the static and final modifiers | 51 |
| Rule | Violation | Line |
|---|---|---|
| LoggerIsNotStaticFinal | The Logger variable declaration does not contain the static and final modifiers | 65 |
| GuardLogStatement | Logger calls should be surrounded by log level guards. | 102 |
| GuardLogStatement | Logger calls should be surrounded by log level guards. | 138 |
| Rule | Violation | Line |
|---|---|---|
| LoggerIsNotStaticFinal | The Logger variable declaration does not contain the static and final modifiers | 66 |
| GuardLogStatement | Logger calls should be surrounded by log level guards. | 78 |
| GuardLogStatement | Logger calls should be surrounded by log level guards. | 86 |
| GuardLogStatement | Logger calls should be surrounded by log level guards. | 94 |
| Rule | Violation | Line |
|---|---|---|
| LoggerIsNotStaticFinal | The Logger variable declaration does not contain the static and final modifiers | 74 |
| GuardLogStatement | Logger calls should be surrounded by log level guards. | 103 |
| GuardLogStatement | Logger calls should be surrounded by log level guards. | 149 |
| GuardLogStatement | Logger calls should be surrounded by log level guards. | 196 |
| GuardLogStatement | Logger calls should be surrounded by log level guards. | 233 |
| Rule | Violation | Line |
|---|---|---|
| AbstractClassWithoutAbstractMethod | This abstract class does not have any abstract methods | 41–76 |
| Rule | Violation | Line |
|---|---|---|
| CommentRequired | Public method and constructor comments are required | 56–59 |
| MissingOverride | The method 'setApiEndPointUrl(String)' is missing an @Override annotation. | 66–69 |
| MissingOverride | The method 'getApiEndPointUrl()' is missing an @Override annotation. | 76–79 |
| AvoidCatchingGenericException | Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block | 100 |
| AvoidDuplicateLiterals | The String literal "LibraryNotificationstore - Error HttpAccessTransport :" appears 6 times in this file; the first occurrence is on line 102 | 102 |
| UseConcurrentHashMap | If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation | 116 |
| AvoidCatchingGenericException | Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block | 125 |
| UseConcurrentHashMap | If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation | 142 |
| AvoidCatchingGenericException | Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block | 151 |
| UseConcurrentHashMap | If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation | 167 |
| AvoidCatchingGenericException | Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block | 176 |
| UseConcurrentHashMap | If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation | 192 |
| AvoidCatchingGenericException | Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block | 201 |
| AvoidCatchingGenericException | Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block | 231 |
| Rule | Violation | Line |
|---|---|---|
| UseConcurrentHashMap | If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation | 104 |
| UseConcurrentHashMap | If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation | 105 |
| UseConcurrentHashMap | If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation | 113 |
| AvoidCatchingGenericException | Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block | 120 |
| Rule | Violation | Line |
|---|---|---|
| UnnecessaryConstructor | Avoid unnecessary constructors - the compiler will generate these for you | 71–73 |
| UncommentedEmptyConstructor | Document empty constructor | 71–73 |
| UseObjectForClearerAPI | Rather than using a lot of String arguments, consider using a container object for those values. | 76 |
| UseObjectForClearerAPI | Rather than using a lot of String arguments, consider using a container object for those values. | 83–84 |
| UseUnderscoresInNumericLiterals | Number 86400000L should separate every third digit with an underscore | 152 |
| UseUnderscoresInNumericLiterals | Number 1672531200000L should separate every third digit with an underscore | 152 |
| ConfusingTernary | Avoid if (x != y) ..; else ..; | 152 |
| UseUnderscoresInNumericLiterals | Number 86400000L should separate every third digit with an underscore | 154 |
| UseUnderscoresInNumericLiterals | Number 1685836800000L should separate every third digit with an underscore | 154 |
| UnusedFormalParameter | Avoid unused method parameters such as 'strIdDemandType'. | 170 |
| UnusedFormalParameter | Avoid unused method parameters such as 'strCustomerId'. | 170 |
| UnusedFormalParameter | Avoid unused method parameters such as 'strIdDemand'. | 170 |
| UseUnderscoresInNumericLiterals | Number 1685836800000L should separate every third digit with an underscore | 177 |
| UseUnderscoresInNumericLiterals | Number 86400000L should separate every third digit with an underscore | 177 |
| ShortVariable | Avoid variables with short names like id | 218 |
| Rule | Violation | Line |
|---|---|---|
| UseObjectForClearerAPI | Rather than using a lot of String arguments, consider using a container object for those values. | 101 |
| UseConcurrentHashMap | If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation | 105 |
| AvoidCatchingGenericException | Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block | 137 |
| PreserveStackTrace | New exception is thrown in catch block, original stack trace may be lost | 140 |
| UseObjectForClearerAPI | Rather than using a lot of String arguments, consider using a container object for those values. | 146–147 |
| UseConcurrentHashMap | If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation | 151 |
| AvoidCatchingGenericException | Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block | 186 |
| PreserveStackTrace | New exception is thrown in catch block, original stack trace may be lost | 189 |
| UseConcurrentHashMap | If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation | 198 |
| AvoidCatchingGenericException | Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block | 220 |
| PreserveStackTrace | New exception is thrown in catch block, original stack trace may be lost | 225 |
| AvoidCatchingGenericException | Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block | 239 |
| PreserveStackTrace | New exception is thrown in catch block, original stack trace may be lost | 242 |
| AvoidCatchingGenericException | Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block | 257 |
| PreserveStackTrace | New exception is thrown in catch block, original stack trace may be lost | 260 |
| AvoidCatchingGenericException | Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block | 275 |
| PreserveStackTrace | New exception is thrown in catch block, original stack trace may be lost | 278 |
| UseConcurrentHashMap | If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation | 287 |
| UseConcurrentHashMap | If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation | 288 |
| AvoidCatchingGenericException | Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block | 306 |
| PreserveStackTrace | New exception is thrown in catch block, original stack trace may be lost | 309 |
| UseConcurrentHashMap | If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation | 318 |
| UseConcurrentHashMap | If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation | 319 |
| AvoidCatchingGenericException | Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block | 337 |
| PreserveStackTrace | New exception is thrown in catch block, original stack trace may be lost | 340 |
| AvoidCatchingGenericException | Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block | 353 |
| PreserveStackTrace | New exception is thrown in catch block, original stack trace may be lost | 356 |
| AvoidCatchingGenericException | Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block | 371 |
| PreserveStackTrace | New exception is thrown in catch block, original stack trace may be lost | 374 |
| AvoidCatchingGenericException | Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block | 389 |
| PreserveStackTrace | New exception is thrown in catch block, original stack trace may be lost | 392 |
| AvoidCatchingGenericException | Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block | 407 |
| PreserveStackTrace | New exception is thrown in catch block, original stack trace may be lost | 410 |
| AvoidCatchingGenericException | Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block | 427 |
| PreserveStackTrace | New exception is thrown in catch block, original stack trace may be lost | 430 |
| AvoidCatchingGenericException | Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block | 446 |
| PreserveStackTrace | New exception is thrown in catch block, original stack trace may be lost | 449 |
| AvoidCatchingGenericException | Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block | 462 |
| PreserveStackTrace | New exception is thrown in catch block, original stack trace may be lost | 465 |
| AvoidCatchingGenericException | Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block | 480 |
| PreserveStackTrace | New exception is thrown in catch block, original stack trace may be lost | 483 |
| AvoidCatchingGenericException | Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block | 498 |
| PreserveStackTrace | New exception is thrown in catch block, original stack trace may be lost | 501 |
| CyclomaticComplexity | The method 'createDemandType(DemandType)' has a cyclomatic complexity of 13. | 506–546 |
| NPathComplexity | The method 'createDemandType(DemandType)' has an NPath complexity of 486 | 506–546 |
| UseConcurrentHashMap | If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation | 510 |
| UseConcurrentHashMap | If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation | 511 |
| AvoidCatchingGenericException | Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block | 541 |
| PreserveStackTrace | New exception is thrown in catch block, original stack trace may be lost | 544 |
| CyclomaticComplexity | The method 'modifyDemandType(DemandType)' has a cyclomatic complexity of 13. | 549–588 |
| NPathComplexity | The method 'modifyDemandType(DemandType)' has an NPath complexity of 486 | 549–588 |
| UseConcurrentHashMap | If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation | 553 |
| UseConcurrentHashMap | If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation | 554 |
| AvoidCatchingGenericException | Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block | 583 |
| PreserveStackTrace | New exception is thrown in catch block, original stack trace may be lost | 586 |
| AvoidCatchingGenericException | Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block | 599 |
| PreserveStackTrace | New exception is thrown in catch block, original stack trace may be lost | 602 |
| Rule | Violation | Line |
|---|---|---|
| UnnecessaryModifier | Unnecessary modifier 'public' on method 'setApiEndPointUrl': the method is declared in an interface type | 113 |
| UnnecessaryModifier | Unnecessary modifier 'public' on method 'getApiEndPointUrl': the method is declared in an interface type | 120 |
| UnnecessaryModifier | Unnecessary modifier 'public' on method 'doDelete': the method is declared in an interface type | 133 |
| Rule | Violation | Line |
|---|---|---|
| UseObjectForClearerAPI | Rather than using a lot of String arguments, consider using a container object for those values. | 63 |
| UseObjectForClearerAPI | Rather than using a lot of String arguments, consider using a container object for those values. | 78 |
| Rule | Violation | Line |
|---|---|---|
| UseObjectForClearerAPI | Rather than using a lot of String arguments, consider using a container object for those values. | 98 |
| UseObjectForClearerAPI | Rather than using a lot of String arguments, consider using a container object for those values. | 117–118 |
| Rule | Violation | Line |
|---|---|---|
| FieldDeclarationsShouldBeAtStartOfClass | Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. | 19 |
| FieldDeclarationsShouldBeAtStartOfClass | Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. | 20 |
| FieldDeclarationsShouldBeAtStartOfClass | Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. | 21 |
| FieldDeclarationsShouldBeAtStartOfClass | Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. | 22 |
| FieldDeclarationsShouldBeAtStartOfClass | Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. | 23 |
| FieldDeclarationsShouldBeAtStartOfClass | Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. | 24 |
| FieldDeclarationsShouldBeAtStartOfClass | Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. | 26 |
| FieldDeclarationsShouldBeAtStartOfClass | Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. | 27 |
| FieldDeclarationsShouldBeAtStartOfClass | Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. | 28 |
| FieldDeclarationsShouldBeAtStartOfClass | Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. | 29 |
| FieldDeclarationsShouldBeAtStartOfClass | Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. | 33 |
| FieldDeclarationsShouldBeAtStartOfClass | Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. | 34 |
| FieldDeclarationsShouldBeAtStartOfClass | Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. | 35 |
| FieldDeclarationsShouldBeAtStartOfClass | Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. | 36 |
| FieldDeclarationsShouldBeAtStartOfClass | Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. | 37 |
| FieldDeclarationsShouldBeAtStartOfClass | Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. | 38 |
| FieldDeclarationsShouldBeAtStartOfClass | Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. | 39 |
| FieldDeclarationsShouldBeAtStartOfClass | Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. | 42 |
| FieldDeclarationsShouldBeAtStartOfClass | Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. | 43 |
| FieldDeclarationsShouldBeAtStartOfClass | Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. | 44 |
| FieldDeclarationsShouldBeAtStartOfClass | Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. | 47 |
| FieldDeclarationsShouldBeAtStartOfClass | Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. | 48 |
| FieldDeclarationsShouldBeAtStartOfClass | Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. | 49 |
| FieldDeclarationsShouldBeAtStartOfClass | Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. | 50 |
| FieldDeclarationsShouldBeAtStartOfClass | Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. | 51 |
| FieldDeclarationsShouldBeAtStartOfClass | Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. | 54 |
| Rule | Violation | Line |
|---|---|---|
| RedundantFieldInitializer | Avoid using redundant field initializer for '_mapper' | 49 |
| NonThreadSafeSingleton | Singleton is not thread safe | 64–69 |
| UnnecessaryLocalBeforeReturn | Consider simply returning the value vs storing it in local variable 'response' | 88 |
| Rule | Violation | Priority | Line |
|---|---|---|---|
| AbstractClassWithoutAbstractMethod | This abstract class does not have any abstract methods | 3 | 41–76 |
| Rule | Violation | Priority | Line |
|---|---|---|---|
| LoggerIsNotStaticFinal | The Logger variable declaration does not contain the static and final modifiers | 2 | 51 |
| CommentRequired | Public method and constructor comments are required | 3 | 56–59 |
| MissingOverride | The method 'setApiEndPointUrl(String)' is missing an @Override annotation. | 3 | 66–69 |
| MissingOverride | The method 'getApiEndPointUrl()' is missing an @Override annotation. | 3 | 76–79 |
| AvoidCatchingGenericException | Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block | 3 | 100 |
| AvoidDuplicateLiterals | The String literal "LibraryNotificationstore - Error HttpAccessTransport :" appears 6 times in this file; the first occurrence is on line 102 | 3 | 102 |
| UseConcurrentHashMap | If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation | 3 | 116 |
| AvoidCatchingGenericException | Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block | 3 | 125 |
| UseConcurrentHashMap | If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation | 3 | 142 |
| AvoidCatchingGenericException | Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block | 3 | 151 |
| UseConcurrentHashMap | If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation | 3 | 167 |
| AvoidCatchingGenericException | Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block | 3 | 176 |
| UseConcurrentHashMap | If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation | 3 | 192 |
| AvoidCatchingGenericException | Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block | 3 | 201 |
| AvoidCatchingGenericException | Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block | 3 | 231 |
| Rule | Violation | Priority | Line |
|---|---|---|---|
| LoggerIsNotStaticFinal | The Logger variable declaration does not contain the static and final modifiers | 2 | 65 |
| GuardLogStatement | Logger calls should be surrounded by log level guards. | 2 | 102 |
| UseConcurrentHashMap | If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation | 3 | 104 |
| UseConcurrentHashMap | If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation | 3 | 105 |
| UseConcurrentHashMap | If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation | 3 | 113 |
| AvoidCatchingGenericException | Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block | 3 | 120 |
| GuardLogStatement | Logger calls should be surrounded by log level guards. | 2 | 138 |
| Rule | Violation | Priority | Line |
|---|---|---|---|
| LoggerIsNotStaticFinal | The Logger variable declaration does not contain the static and final modifiers | 2 | 66 |
| UnnecessaryConstructor | Avoid unnecessary constructors - the compiler will generate these for you | 3 | 71–73 |
| UncommentedEmptyConstructor | Document empty constructor | 3 | 71–73 |
| UseObjectForClearerAPI | Rather than using a lot of String arguments, consider using a container object for those values. | 3 | 76 |
| GuardLogStatement | Logger calls should be surrounded by log level guards. | 2 | 78 |
| UseObjectForClearerAPI | Rather than using a lot of String arguments, consider using a container object for those values. | 3 | 83–84 |
| GuardLogStatement | Logger calls should be surrounded by log level guards. | 2 | 86 |
| GuardLogStatement | Logger calls should be surrounded by log level guards. | 2 | 94 |
| UseUnderscoresInNumericLiterals | Number 86400000L should separate every third digit with an underscore | 3 | 152 |
| UseUnderscoresInNumericLiterals | Number 1672531200000L should separate every third digit with an underscore | 3 | 152 |
| ConfusingTernary | Avoid if (x != y) ..; else ..; | 3 | 152 |
| UseUnderscoresInNumericLiterals | Number 86400000L should separate every third digit with an underscore | 3 | 154 |
| UseUnderscoresInNumericLiterals | Number 1685836800000L should separate every third digit with an underscore | 3 | 154 |
| UnusedFormalParameter | Avoid unused method parameters such as 'strIdDemandType'. | 3 | 170 |
| UnusedFormalParameter | Avoid unused method parameters such as 'strCustomerId'. | 3 | 170 |
| UnusedFormalParameter | Avoid unused method parameters such as 'strIdDemand'. | 3 | 170 |
| UseUnderscoresInNumericLiterals | Number 1685836800000L should separate every third digit with an underscore | 3 | 177 |
| UseUnderscoresInNumericLiterals | Number 86400000L should separate every third digit with an underscore | 3 | 177 |
| ShortVariable | Avoid variables with short names like id | 3 | 218 |
| Rule | Violation | Priority | Line |
|---|---|---|---|
| LoggerIsNotStaticFinal | The Logger variable declaration does not contain the static and final modifiers | 2 | 74 |
| UseObjectForClearerAPI | Rather than using a lot of String arguments, consider using a container object for those values. | 3 | 101 |
| GuardLogStatement | Logger calls should be surrounded by log level guards. | 2 | 103 |
| UseConcurrentHashMap | If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation | 3 | 105 |
| AvoidCatchingGenericException | Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block | 3 | 137 |
| PreserveStackTrace | New exception is thrown in catch block, original stack trace may be lost | 3 | 140 |
| UseObjectForClearerAPI | Rather than using a lot of String arguments, consider using a container object for those values. | 3 | 146–147 |
| GuardLogStatement | Logger calls should be surrounded by log level guards. | 2 | 149 |
| UseConcurrentHashMap | If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation | 3 | 151 |
| AvoidCatchingGenericException | Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block | 3 | 186 |
| PreserveStackTrace | New exception is thrown in catch block, original stack trace may be lost | 3 | 189 |
| GuardLogStatement | Logger calls should be surrounded by log level guards. | 2 | 196 |
| UseConcurrentHashMap | If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation | 3 | 198 |
| AvoidCatchingGenericException | Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block | 3 | 220 |
| PreserveStackTrace | New exception is thrown in catch block, original stack trace may be lost | 3 | 225 |
| GuardLogStatement | Logger calls should be surrounded by log level guards. | 2 | 233 |
| AvoidCatchingGenericException | Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block | 3 | 239 |
| PreserveStackTrace | New exception is thrown in catch block, original stack trace may be lost | 3 | 242 |
| AvoidCatchingGenericException | Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block | 3 | 257 |
| PreserveStackTrace | New exception is thrown in catch block, original stack trace may be lost | 3 | 260 |
| AvoidCatchingGenericException | Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block | 3 | 275 |
| PreserveStackTrace | New exception is thrown in catch block, original stack trace may be lost | 3 | 278 |
| UseConcurrentHashMap | If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation | 3 | 287 |
| UseConcurrentHashMap | If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation | 3 | 288 |
| AvoidCatchingGenericException | Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block | 3 | 306 |
| PreserveStackTrace | New exception is thrown in catch block, original stack trace may be lost | 3 | 309 |
| UseConcurrentHashMap | If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation | 3 | 318 |
| UseConcurrentHashMap | If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation | 3 | 319 |
| AvoidCatchingGenericException | Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block | 3 | 337 |
| PreserveStackTrace | New exception is thrown in catch block, original stack trace may be lost | 3 | 340 |
| AvoidCatchingGenericException | Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block | 3 | 353 |
| PreserveStackTrace | New exception is thrown in catch block, original stack trace may be lost | 3 | 356 |
| AvoidCatchingGenericException | Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block | 3 | 371 |
| PreserveStackTrace | New exception is thrown in catch block, original stack trace may be lost | 3 | 374 |
| AvoidCatchingGenericException | Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block | 3 | 389 |
| PreserveStackTrace | New exception is thrown in catch block, original stack trace may be lost | 3 | 392 |
| AvoidCatchingGenericException | Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block | 3 | 407 |
| PreserveStackTrace | New exception is thrown in catch block, original stack trace may be lost | 3 | 410 |
| AvoidCatchingGenericException | Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block | 3 | 427 |
| PreserveStackTrace | New exception is thrown in catch block, original stack trace may be lost | 3 | 430 |
| AvoidCatchingGenericException | Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block | 3 | 446 |
| PreserveStackTrace | New exception is thrown in catch block, original stack trace may be lost | 3 | 449 |
| AvoidCatchingGenericException | Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block | 3 | 462 |
| PreserveStackTrace | New exception is thrown in catch block, original stack trace may be lost | 3 | 465 |
| AvoidCatchingGenericException | Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block | 3 | 480 |
| PreserveStackTrace | New exception is thrown in catch block, original stack trace may be lost | 3 | 483 |
| AvoidCatchingGenericException | Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block | 3 | 498 |
| PreserveStackTrace | New exception is thrown in catch block, original stack trace may be lost | 3 | 501 |
| CyclomaticComplexity | The method 'createDemandType(DemandType)' has a cyclomatic complexity of 13. | 3 | 506–546 |
| NPathComplexity | The method 'createDemandType(DemandType)' has an NPath complexity of 486 | 3 | 506–546 |
| UseConcurrentHashMap | If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation | 3 | 510 |
| UseConcurrentHashMap | If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation | 3 | 511 |
| AvoidCatchingGenericException | Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block | 3 | 541 |
| PreserveStackTrace | New exception is thrown in catch block, original stack trace may be lost | 3 | 544 |
| CyclomaticComplexity | The method 'modifyDemandType(DemandType)' has a cyclomatic complexity of 13. | 3 | 549–588 |
| NPathComplexity | The method 'modifyDemandType(DemandType)' has an NPath complexity of 486 | 3 | 549–588 |
| UseConcurrentHashMap | If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation | 3 | 553 |
| UseConcurrentHashMap | If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation | 3 | 554 |
| AvoidCatchingGenericException | Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block | 3 | 583 |
| PreserveStackTrace | New exception is thrown in catch block, original stack trace may be lost | 3 | 586 |
| AvoidCatchingGenericException | Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block | 3 | 599 |
| PreserveStackTrace | New exception is thrown in catch block, original stack trace may be lost | 3 | 602 |
| Rule | Violation | Priority | Line |
|---|---|---|---|
| UnnecessaryModifier | Unnecessary modifier 'public' on method 'setApiEndPointUrl': the method is declared in an interface type | 3 | 113 |
| UnnecessaryModifier | Unnecessary modifier 'public' on method 'getApiEndPointUrl': the method is declared in an interface type | 3 | 120 |
| UnnecessaryModifier | Unnecessary modifier 'public' on method 'doDelete': the method is declared in an interface type | 3 | 133 |
| Rule | Violation | Priority | Line |
|---|---|---|---|
| UseObjectForClearerAPI | Rather than using a lot of String arguments, consider using a container object for those values. | 3 | 63 |
| UseObjectForClearerAPI | Rather than using a lot of String arguments, consider using a container object for those values. | 3 | 78 |
| Rule | Violation | Priority | Line |
|---|---|---|---|
| UseObjectForClearerAPI | Rather than using a lot of String arguments, consider using a container object for those values. | 3 | 98 |
| UseObjectForClearerAPI | Rather than using a lot of String arguments, consider using a container object for those values. | 3 | 117–118 |
| Rule | Violation | Priority | Line |
|---|---|---|---|
| ClassWithOnlyPrivateConstructorsShouldBeFinal | A class which only has private constructors should be final | 1 | 8–55 |
| ClassNamingConventions | The utility class name 'NotificationStoreConstants' doesn't match '[A-Z][a-zA-Z0-9]+(Utils?|Helper|Home|Service)' | 1 | 8–55 |
| FieldDeclarationsShouldBeAtStartOfClass | Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. | 3 | 19 |
| FieldDeclarationsShouldBeAtStartOfClass | Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. | 3 | 20 |
| FieldDeclarationsShouldBeAtStartOfClass | Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. | 3 | 21 |
| FieldDeclarationsShouldBeAtStartOfClass | Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. | 3 | 22 |
| FieldDeclarationsShouldBeAtStartOfClass | Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. | 3 | 23 |
| FieldDeclarationsShouldBeAtStartOfClass | Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. | 3 | 24 |
| FieldDeclarationsShouldBeAtStartOfClass | Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. | 3 | 26 |
| FieldDeclarationsShouldBeAtStartOfClass | Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. | 3 | 27 |
| FieldDeclarationsShouldBeAtStartOfClass | Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. | 3 | 28 |
| FieldDeclarationsShouldBeAtStartOfClass | Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. | 3 | 29 |
| FieldDeclarationsShouldBeAtStartOfClass | Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. | 3 | 33 |
| FieldDeclarationsShouldBeAtStartOfClass | Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. | 3 | 34 |
| FieldDeclarationsShouldBeAtStartOfClass | Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. | 3 | 35 |
| FieldDeclarationsShouldBeAtStartOfClass | Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. | 3 | 36 |
| FieldDeclarationsShouldBeAtStartOfClass | Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. | 3 | 37 |
| FieldDeclarationsShouldBeAtStartOfClass | Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. | 3 | 38 |
| FieldDeclarationsShouldBeAtStartOfClass | Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. | 3 | 39 |
| FieldDeclarationsShouldBeAtStartOfClass | Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. | 3 | 42 |
| FieldDeclarationsShouldBeAtStartOfClass | Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. | 3 | 43 |
| FieldDeclarationsShouldBeAtStartOfClass | Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. | 3 | 44 |
| FieldDeclarationsShouldBeAtStartOfClass | Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. | 3 | 47 |
| FieldDeclarationsShouldBeAtStartOfClass | Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. | 3 | 48 |
| FieldDeclarationsShouldBeAtStartOfClass | Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. | 3 | 49 |
| FieldDeclarationsShouldBeAtStartOfClass | Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. | 3 | 50 |
| FieldDeclarationsShouldBeAtStartOfClass | Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. | 3 | 51 |
| FieldDeclarationsShouldBeAtStartOfClass | Fields should be declared at the top of the class, before any method declarations, constructors, initializers or inner classes. | 3 | 54 |
| Rule | Violation | Priority | Line |
|---|---|---|---|
| ClassWithOnlyPrivateConstructorsShouldBeFinal | A class which only has private constructors should be final | 1 | 47–91 |
| RedundantFieldInitializer | Avoid using redundant field initializer for '_mapper' | 3 | 49 |
| NonThreadSafeSingleton | Singleton is not thread safe | 3 | 64–69 |
| UnnecessaryLocalBeforeReturn | Consider simply returning the value vs storing it in local variable 'response' | 3 | 88 |
