Fork me on GitHub

PMD Results

The following document contains the results of PMD 6.13.0.

Violations By Priority

Priority 1

fr/paris/lutece/plugins/appointment/modules/rest/pojo/AppointmentSlotSolrPOJO.java

Rule Violation Line
ClassWithOnlyPrivateConstructorsShouldBeFinal A class which only has private constructors should be final 38–85

fr/paris/lutece/plugins/appointment/modules/rest/pojo/SolrAppointmentSlotPOJO.java

Rule Violation Line
ClassWithOnlyPrivateConstructorsShouldBeFinal A class which only has private constructors should be final 38–150

fr/paris/lutece/plugins/appointment/modules/rest/rs/filter/QueryParamValidator.java

Rule Violation Line
ClassNamingConventions The utility class name 'QueryParamValidator' doesn't match '[A-Z][a-zA-Z0-9]+(Utils?|Helper|Home|Service)' 44–106
ClassWithOnlyPrivateConstructorsShouldBeFinal A class which only has private constructors should be final 44–106

fr/paris/lutece/plugins/appointment/modules/rest/service/AppointmentSlotsService.java

Rule Violation Line
ClassWithOnlyPrivateConstructorsShouldBeFinal A class which only has private constructors should be final 61–153

fr/paris/lutece/plugins/appointment/modules/rest/util/contsants/AppointmentRestConstants.java

Rule Violation Line
ClassWithOnlyPrivateConstructorsShouldBeFinal A class which only has private constructors should be final 38–89
ClassNamingConventions The utility class name 'AppointmentRestConstants' doesn't match '[A-Z][a-zA-Z0-9]+(Utils?|Helper|Home|Service)' 38–89

Priority 3

fr/paris/lutece/plugins/appointment/modules/rest/business/providers/IAppointmentDataProvider.java

Rule Violation Line
CommentRequired Header comments are required 42–72

fr/paris/lutece/plugins/appointment/modules/rest/business/providers/SolrProvider.java

Rule Violation Line
CommentRequired Header comments are required 56–216
AvoidSynchronizedAtMethodLevel Use block level rather than method level synchronization 79–88
CommentRequired Public method and constructor comments are required 79–88
AvoidSynchronizedAtMethodLevel Use block level rather than method level synchronization 90–99
ConsecutiveAppendsShouldReuse StringBuffer (or StringBuilder).append is called consecutively without reusing the target variable. 130–131
ConsecutiveAppendsShouldReuse StringBuffer (or StringBuilder).append is called consecutively without reusing the target variable. 132
ConsecutiveAppendsShouldReuse StringBuffer (or StringBuilder).append is called consecutively without reusing the target variable. 133–134
ConsecutiveAppendsShouldReuse StringBuffer (or StringBuilder).append is called consecutively without reusing the target variable. 135
ConsecutiveAppendsShouldReuse StringBuffer (or StringBuilder).append is called consecutively without reusing the target variable. 136
ConsecutiveAppendsShouldReuse StringBuffer (or StringBuilder).append is called consecutively without reusing the target variable. 137–139
ConsecutiveAppendsShouldReuse StringBuffer (or StringBuilder).append is called consecutively without reusing the target variable. 140
ConsecutiveAppendsShouldReuse StringBuffer (or StringBuilder).append is called consecutively without reusing the target variable. 141–142
ConsecutiveAppendsShouldReuse StringBuffer (or StringBuilder).append is called consecutively without reusing the target variable. 143
ConsecutiveAppendsShouldReuse StringBuffer (or StringBuilder).append is called consecutively without reusing the target variable. 144
ConsecutiveAppendsShouldReuse StringBuffer (or StringBuilder).append is called consecutively without reusing the target variable. 145
ConsecutiveAppendsShouldReuse StringBuffer (or StringBuilder).append is called consecutively without reusing the target variable. 146–147
ConsecutiveAppendsShouldReuse StringBuffer (or StringBuilder).append is called consecutively without reusing the target variable. 148
ConsecutiveAppendsShouldReuse StringBuffer (or StringBuilder).append is called consecutively without reusing the target variable. 149–150
ConsecutiveAppendsShouldReuse StringBuffer (or StringBuilder).append is called consecutively without reusing the target variable. 151
ConsecutiveAppendsShouldReuse StringBuffer (or StringBuilder).append is called consecutively without reusing the target variable. 152–153
ConsecutiveAppendsShouldReuse StringBuffer (or StringBuilder).append is called consecutively without reusing the target variable. 154
ConsecutiveAppendsShouldReuse StringBuffer (or StringBuilder).append is called consecutively without reusing the target variable. 155
ConsecutiveAppendsShouldReuse StringBuffer (or StringBuilder).append is called consecutively without reusing the target variable. 156–157
ConsecutiveAppendsShouldReuse StringBuffer (or StringBuilder).append is called consecutively without reusing the target variable. 158
ConsecutiveAppendsShouldReuse StringBuffer (or StringBuilder).append is called consecutively without reusing the target variable. 159
ConsecutiveAppendsShouldReuse StringBuffer (or StringBuilder).append is called consecutively without reusing the target variable. 160–161
ConsecutiveAppendsShouldReuse StringBuffer (or StringBuilder).append is called consecutively without reusing the target variable. 183–184
ConsecutiveAppendsShouldReuse StringBuffer (or StringBuilder).append is called consecutively without reusing the target variable. 185
ConsecutiveAppendsShouldReuse StringBuffer (or StringBuilder).append is called consecutively without reusing the target variable. 186–187
ConsecutiveAppendsShouldReuse StringBuffer (or StringBuilder).append is called consecutively without reusing the target variable. 188
ConsecutiveAppendsShouldReuse StringBuffer (or StringBuilder).append is called consecutively without reusing the target variable. 189–190
ConsecutiveAppendsShouldReuse StringBuffer (or StringBuilder).append is called consecutively without reusing the target variable. 191
CommentRequired Public method and constructor comments are required 196–210
CommentRequired Public method and constructor comments are required 212–215

fr/paris/lutece/plugins/appointment/modules/rest/pojo/AppointmentSlotSolrPOJO.java

Rule Violation Line
CommentRequired Header comments are required 38–85
DefaultPackage Use explicit scoping instead of the default package private level 45–46
CommentDefaultAccessModifier To avoid mistakes add a comment at the beginning of the _strUidFormString field if you want a default access modifier 46
DefaultPackage Use explicit scoping instead of the default package private level 47–48
CommentDefaultAccessModifier To avoid mistakes add a comment at the beginning of the _strDate field if you want a default access modifier 48
DefaultPackage Use explicit scoping instead of the default package private level 49–50
CommentDefaultAccessModifier To avoid mistakes add a comment at the beginning of the _strUrl field if you want a default access modifier 50
CommentRequired Public method and constructor comments are required 56–59
CommentRequired Public method and constructor comments are required 61–64
CommentRequired Public method and constructor comments are required 66–69
CommentRequired Public method and constructor comments are required 71–74
CommentRequired Public method and constructor comments are required 76–79
CommentRequired Public method and constructor comments are required 81–84

fr/paris/lutece/plugins/appointment/modules/rest/pojo/AppointmentSlotsSearchPOJO.java

Rule Violation Line
DataClass The class 'AppointmentSlotsSearchPOJO' is suspected to be a Data Class (WOC=30.769%, NOPA=0, NOAM=6, WMC=13) 39–116
CommentRequired Header comments are required 39–116
UncommentedEmptyConstructor Document empty constructor 47–49
CommentRequired Public method and constructor comments are required 47–49
CommentRequired Public method and constructor comments are required 51–56
CommentRequired Public method and constructor comments are required 58–65
CommentRequired Public method and constructor comments are required 97–100
CommentRequired Public method and constructor comments are required 102–105
CommentRequired Public method and constructor comments are required 107–110
CommentRequired Public method and constructor comments are required 112–115

fr/paris/lutece/plugins/appointment/modules/rest/pojo/InfoSlot.java

Rule Violation Line
CommentRequired Header comments are required 43–80
UncommentedEmptyConstructor Document empty constructor 51–53
CommentRequired Public method and constructor comments are required 51–53
CommentRequired Public method and constructor comments are required 55–59
CommentRequired Public method and constructor comments are required 71–74
CommentRequired Public method and constructor comments are required 76–79

fr/paris/lutece/plugins/appointment/modules/rest/pojo/MeetingPointPOJO.java

Rule Violation Line
CommentRequired Header comments are required 40–171
CommentRequired Public method and constructor comments are required 64–66
UncommentedEmptyConstructor Document empty constructor 64–66
CommentRequired Public method and constructor comments are required 68–80
CommentRequired Public method and constructor comments are required 82–85
CommentRequired Public method and constructor comments are required 87–90
CommentRequired Public method and constructor comments are required 92–95
CommentRequired Public method and constructor comments are required 97–100
CommentRequired Public method and constructor comments are required 102–105
CommentRequired Public method and constructor comments are required 107–110
CommentRequired Public method and constructor comments are required 112–115
CommentRequired Public method and constructor comments are required 117–120
CommentRequired Public method and constructor comments are required 122–125
CommentRequired Public method and constructor comments are required 127–130
CommentRequired Public method and constructor comments are required 132–135
CommentRequired Public method and constructor comments are required 137–140
CommentRequired Public method and constructor comments are required 142–145
CommentRequired Public method and constructor comments are required 147–150
CommentRequired Public method and constructor comments are required 152–155
CommentRequired Public method and constructor comments are required 157–160
CommentRequired Public method and constructor comments are required 162–165
CommentRequired Public method and constructor comments are required 167–170

fr/paris/lutece/plugins/appointment/modules/rest/pojo/SolrAppointmentSlotPOJO.java

Rule Violation Line
CommentRequired Header comments are required 38–150
DefaultPackage Use explicit scoping instead of the default package private level 50–51
CommentDefaultAccessModifier To avoid mistakes add a comment at the beginning of the _strUidFormString field if you want a default access modifier 51
DefaultPackage Use explicit scoping instead of the default package private level 52–53
CommentDefaultAccessModifier To avoid mistakes add a comment at the beginning of the _strDate field if you want a default access modifier 53
DefaultPackage Use explicit scoping instead of the default package private level 54–55
CommentDefaultAccessModifier To avoid mistakes add a comment at the beginning of the _strUrl field if you want a default access modifier 55
DefaultPackage Use explicit scoping instead of the default package private level 56–57
CommentDefaultAccessModifier To avoid mistakes add a comment at the beginning of the _strDayOpen field if you want a default access modifier 57
DefaultPackage Use explicit scoping instead of the default package private level 58–59
CommentDefaultAccessModifier To avoid mistakes add a comment at the beginning of the _strEnabled field if you want a default access modifier 59
DefaultPackage Use explicit scoping instead of the default package private level 60–61
CommentDefaultAccessModifier To avoid mistakes add a comment at the beginning of the _strAppointmentActive field if you want a default access modifier 61
DefaultPackage Use explicit scoping instead of the default package private level 62–63
CommentDefaultAccessModifier To avoid mistakes add a comment at the beginning of the _lNbConsecutivesSlots field if you want a default access modifier 63
DefaultPackage Use explicit scoping instead of the default package private level 64–65
CommentDefaultAccessModifier To avoid mistakes add a comment at the beginning of the _lMaxConsecutivesSlots field if you want a default access modifier 65
CommentRequired Public method and constructor comments are required 71–74
CommentRequired Public method and constructor comments are required 76–79
CommentRequired Public method and constructor comments are required 81–84
CommentRequired Public method and constructor comments are required 86–89
CommentRequired Public method and constructor comments are required 91–94
CommentRequired Public method and constructor comments are required 96–99
CommentRequired Public method and constructor comments are required 101–104
CommentRequired Public method and constructor comments are required 106–109
CommentRequired Public method and constructor comments are required 111–114
CommentRequired Public method and constructor comments are required 116–119
CommentRequired Public method and constructor comments are required 121–124
CommentRequired Public method and constructor comments are required 126–129
CommentRequired Public method and constructor comments are required 131–134
CommentRequired Public method and constructor comments are required 136–139
CommentRequired Public method and constructor comments are required 146–149

fr/paris/lutece/plugins/appointment/modules/rest/pojo/SolrMeetingPointPOJO.java

Rule Violation Line
CommentRequired Header comments are required 40–110
DefaultPackage Use explicit scoping instead of the default package private level 50–51
CommentDefaultAccessModifier To avoid mistakes add a comment at the beginning of the _strUid field if you want a default access modifier 51
DefaultPackage Use explicit scoping instead of the default package private level 52–53
CommentDefaultAccessModifier To avoid mistakes add a comment at the beginning of the _strTitle field if you want a default access modifier 53
DefaultPackage Use explicit scoping instead of the default package private level 54–55
CommentDefaultAccessModifier To avoid mistakes add a comment at the beginning of the _strAddressText field if you want a default access modifier 55
DefaultPackage Use explicit scoping instead of the default package private level 56–57
CommentDefaultAccessModifier To avoid mistakes add a comment at the beginning of the _strGeoloc field if you want a default access modifier 57
DefaultPackage Use explicit scoping instead of the default package private level 58–59
CommentDefaultAccessModifier To avoid mistakes add a comment at the beginning of the _strIconUrl field if you want a default access modifier 59
CommentRequired Public method and constructor comments are required 61–64
CommentRequired Public method and constructor comments are required 66–69
CommentRequired Public method and constructor comments are required 71–74
CommentRequired Public method and constructor comments are required 76–79
CommentRequired Public method and constructor comments are required 81–84
CommentRequired Public method and constructor comments are required 86–89
CommentRequired Public method and constructor comments are required 91–94
CommentRequired Public method and constructor comments are required 96–99
CommentRequired Public method and constructor comments are required 101–104
CommentRequired Public method and constructor comments are required 106–109

fr/paris/lutece/plugins/appointment/modules/rest/pojo/SolrResponseMeetingPointPOJO.java

Rule Violation Line
CommentRequired Header comments are required 41–142
CommentRequired Header comments are required 58–73
CommentRequired Header comments are required 76–92
CommentRequired Header comments are required 95–123
DataClass The class 'Group' is suspected to be a Data Class (WOC=0.000%, NOPA=0, NOAM=4, WMC=4) 95–123
CommentRequired Header comments are required 126–141

fr/paris/lutece/plugins/appointment/modules/rest/rs/AppointmentRest.java

Rule Violation Line
CommentRequired Header comments are required 64–133
DefaultPackage Use explicit scoping instead of the default package private level 70–71
CommentDefaultAccessModifier To avoid mistakes add a comment at the beginning of the _appointmentRestService field if you want a default access modifier 71
UseObjectForClearerAPI Rather than using a lot of String arguments, consider using a container object for those values. 76–81
CommentRequired Public method and constructor comments are required 76–108
UnnecessaryAnnotationValueElement Avoid the use of value in annotations when its the only element 77
UnnecessaryAnnotationValueElement Avoid the use of value in annotations when its the only element 78
UnnecessaryAnnotationValueElement Avoid the use of value in annotations when its the only element 79
UnnecessaryAnnotationValueElement Avoid the use of value in annotations when its the only element 80
UnnecessaryAnnotationValueElement Avoid the use of value in annotations when its the only element 81
PreserveStackTrace New exception is thrown in catch block, original stack trace may be lost 99–100
PreserveStackTrace New exception is thrown in catch block, original stack trace may be lost 104–105
CommentRequired Public method and constructor comments are required 114–132
PreserveStackTrace New exception is thrown in catch block, original stack trace may be lost 123–124
PreserveStackTrace New exception is thrown in catch block, original stack trace may be lost 128–129

fr/paris/lutece/plugins/appointment/modules/rest/rs/filter/QueryParamValidator.java

Rule Violation Line
CommentRequired Header comments are required 44–106
CommentRequired Public method and constructor comments are required 58–92
ConfusingTernary Avoid if (x != y) ..; else ..; 69–79
ConfusingTernary Avoid if (x != y) ..; else ..; 80–90
CommentRequired Public method and constructor comments are required 94–105

fr/paris/lutece/plugins/appointment/modules/rest/rs/filter/ValidationErrorResponse.java

Rule Violation Line
CommentRequired Header comments are required 39–108
ShortVariable Avoid variables with short names like d 53
CommentRequired Public method and constructor comments are required 53–56
CommentRequired Header comments are required 58–107
DataClass The class 'Detail' is suspected to be a Data Class (WOC=0.000%, NOPA=0, NOAM=6, WMC=8) 58–107
CommentDefaultAccessModifier To avoid mistakes add a comment at the beginning of the Detail nested class if you want a default access modifier 58–107
CommentRequired Public method and constructor comments are required 64–69
CommentRequired Public method and constructor comments are required 71–76

fr/paris/lutece/plugins/appointment/modules/rest/service/AppointmentMeetingPointsService.java

Rule Violation Line
CommentRequired Header comments are required 54–165
CommentRequired Public method and constructor comments are required 64–73
AvoidSynchronizedAtMethodLevel Use block level rather than method level synchronization 64–73
AvoidSynchronizedAtMethodLevel Use block level rather than method level synchronization 75–84
CommentRequired Public method and constructor comments are required 86–119
CommentRequired Public method and constructor comments are required 121–163

fr/paris/lutece/plugins/appointment/modules/rest/service/AppointmentRestService.java

Rule Violation Line
CommentRequired Header comments are required 45–62

fr/paris/lutece/plugins/appointment/modules/rest/service/AppointmentSlotsService.java

Rule Violation Line
CommentRequired Header comments are required 61–153
CommentRequired Public method and constructor comments are required 74–84
AvoidSynchronizedAtMethodLevel Use block level rather than method level synchronization 74–84
AvoidSynchronizedAtMethodLevel Use block level rather than method level synchronization 86–93
CommentRequired Public method and constructor comments are required 95–117
CommentRequired Public method and constructor comments are required 125–135

fr/paris/lutece/plugins/appointment/modules/rest/service/IAppointmentRestService.java

Rule Violation Line
CommentRequired Header comments are required 45–50
UnnecessaryModifier Unnecessary modifier 'public' on method 'getAvailableTimeSlots': the method is declared in an interface type 47
CommentRequired Public method and constructor comments are required 47
CommentRequired Public method and constructor comments are required 49
UnnecessaryModifier Unnecessary modifier 'public' on method 'getManagedMeetingPoints': the method is declared in an interface type 49

fr/paris/lutece/plugins/appointment/modules/rest/util/contsants/AppointmentRestConstants.java

Rule Violation Line
CommentRequired Header comments are required 38–89

Priority 4

fr/paris/lutece/plugins/appointment/modules/rest/service/AppointmentMeetingPointsService.java

Rule Violation Line
UnusedImports Avoid unused imports such as 'com.fasterxml.jackson.core.JsonProcessingException' 36

Files

fr/paris/lutece/plugins/appointment/modules/rest/business/providers/IAppointmentDataProvider.java

Rule Violation Priority Line
CommentRequired Header comments are required 3 42–72

fr/paris/lutece/plugins/appointment/modules/rest/business/providers/SolrProvider.java

Rule Violation Priority Line
CommentRequired Header comments are required 3 56–216
AvoidSynchronizedAtMethodLevel Use block level rather than method level synchronization 3 79–88
CommentRequired Public method and constructor comments are required 3 79–88
AvoidSynchronizedAtMethodLevel Use block level rather than method level synchronization 3 90–99
ConsecutiveAppendsShouldReuse StringBuffer (or StringBuilder).append is called consecutively without reusing the target variable. 3 130–131
ConsecutiveAppendsShouldReuse StringBuffer (or StringBuilder).append is called consecutively without reusing the target variable. 3 132
ConsecutiveAppendsShouldReuse StringBuffer (or StringBuilder).append is called consecutively without reusing the target variable. 3 133–134
ConsecutiveAppendsShouldReuse StringBuffer (or StringBuilder).append is called consecutively without reusing the target variable. 3 135
ConsecutiveAppendsShouldReuse StringBuffer (or StringBuilder).append is called consecutively without reusing the target variable. 3 136
ConsecutiveAppendsShouldReuse StringBuffer (or StringBuilder).append is called consecutively without reusing the target variable. 3 137–139
ConsecutiveAppendsShouldReuse StringBuffer (or StringBuilder).append is called consecutively without reusing the target variable. 3 140
ConsecutiveAppendsShouldReuse StringBuffer (or StringBuilder).append is called consecutively without reusing the target variable. 3 141–142
ConsecutiveAppendsShouldReuse StringBuffer (or StringBuilder).append is called consecutively without reusing the target variable. 3 143
ConsecutiveAppendsShouldReuse StringBuffer (or StringBuilder).append is called consecutively without reusing the target variable. 3 144
ConsecutiveAppendsShouldReuse StringBuffer (or StringBuilder).append is called consecutively without reusing the target variable. 3 145
ConsecutiveAppendsShouldReuse StringBuffer (or StringBuilder).append is called consecutively without reusing the target variable. 3 146–147
ConsecutiveAppendsShouldReuse StringBuffer (or StringBuilder).append is called consecutively without reusing the target variable. 3 148
ConsecutiveAppendsShouldReuse StringBuffer (or StringBuilder).append is called consecutively without reusing the target variable. 3 149–150
ConsecutiveAppendsShouldReuse StringBuffer (or StringBuilder).append is called consecutively without reusing the target variable. 3 151
ConsecutiveAppendsShouldReuse StringBuffer (or StringBuilder).append is called consecutively without reusing the target variable. 3 152–153
ConsecutiveAppendsShouldReuse StringBuffer (or StringBuilder).append is called consecutively without reusing the target variable. 3 154
ConsecutiveAppendsShouldReuse StringBuffer (or StringBuilder).append is called consecutively without reusing the target variable. 3 155
ConsecutiveAppendsShouldReuse StringBuffer (or StringBuilder).append is called consecutively without reusing the target variable. 3 156–157
ConsecutiveAppendsShouldReuse StringBuffer (or StringBuilder).append is called consecutively without reusing the target variable. 3 158
ConsecutiveAppendsShouldReuse StringBuffer (or StringBuilder).append is called consecutively without reusing the target variable. 3 159
ConsecutiveAppendsShouldReuse StringBuffer (or StringBuilder).append is called consecutively without reusing the target variable. 3 160–161
ConsecutiveAppendsShouldReuse StringBuffer (or StringBuilder).append is called consecutively without reusing the target variable. 3 183–184
ConsecutiveAppendsShouldReuse StringBuffer (or StringBuilder).append is called consecutively without reusing the target variable. 3 185
ConsecutiveAppendsShouldReuse StringBuffer (or StringBuilder).append is called consecutively without reusing the target variable. 3 186–187
ConsecutiveAppendsShouldReuse StringBuffer (or StringBuilder).append is called consecutively without reusing the target variable. 3 188
ConsecutiveAppendsShouldReuse StringBuffer (or StringBuilder).append is called consecutively without reusing the target variable. 3 189–190
ConsecutiveAppendsShouldReuse StringBuffer (or StringBuilder).append is called consecutively without reusing the target variable. 3 191
CommentRequired Public method and constructor comments are required 3 196–210
CommentRequired Public method and constructor comments are required 3 212–215

fr/paris/lutece/plugins/appointment/modules/rest/pojo/AppointmentSlotSolrPOJO.java

Rule Violation Priority Line
ClassWithOnlyPrivateConstructorsShouldBeFinal A class which only has private constructors should be final 1 38–85
CommentRequired Header comments are required 3 38–85
DefaultPackage Use explicit scoping instead of the default package private level 3 45–46
CommentDefaultAccessModifier To avoid mistakes add a comment at the beginning of the _strUidFormString field if you want a default access modifier 3 46
DefaultPackage Use explicit scoping instead of the default package private level 3 47–48
CommentDefaultAccessModifier To avoid mistakes add a comment at the beginning of the _strDate field if you want a default access modifier 3 48
DefaultPackage Use explicit scoping instead of the default package private level 3 49–50
CommentDefaultAccessModifier To avoid mistakes add a comment at the beginning of the _strUrl field if you want a default access modifier 3 50
CommentRequired Public method and constructor comments are required 3 56–59
CommentRequired Public method and constructor comments are required 3 61–64
CommentRequired Public method and constructor comments are required 3 66–69
CommentRequired Public method and constructor comments are required 3 71–74
CommentRequired Public method and constructor comments are required 3 76–79
CommentRequired Public method and constructor comments are required 3 81–84

fr/paris/lutece/plugins/appointment/modules/rest/pojo/AppointmentSlotsSearchPOJO.java

Rule Violation Priority Line
DataClass The class 'AppointmentSlotsSearchPOJO' is suspected to be a Data Class (WOC=30.769%, NOPA=0, NOAM=6, WMC=13) 3 39–116
CommentRequired Header comments are required 3 39–116
UncommentedEmptyConstructor Document empty constructor 3 47–49
CommentRequired Public method and constructor comments are required 3 47–49
CommentRequired Public method and constructor comments are required 3 51–56
CommentRequired Public method and constructor comments are required 3 58–65
CommentRequired Public method and constructor comments are required 3 97–100
CommentRequired Public method and constructor comments are required 3 102–105
CommentRequired Public method and constructor comments are required 3 107–110
CommentRequired Public method and constructor comments are required 3 112–115

fr/paris/lutece/plugins/appointment/modules/rest/pojo/InfoSlot.java

Rule Violation Priority Line
CommentRequired Header comments are required 3 43–80
UncommentedEmptyConstructor Document empty constructor 3 51–53
CommentRequired Public method and constructor comments are required 3 51–53
CommentRequired Public method and constructor comments are required 3 55–59
CommentRequired Public method and constructor comments are required 3 71–74
CommentRequired Public method and constructor comments are required 3 76–79

fr/paris/lutece/plugins/appointment/modules/rest/pojo/MeetingPointPOJO.java

Rule Violation Priority Line
CommentRequired Header comments are required 3 40–171
CommentRequired Public method and constructor comments are required 3 64–66
UncommentedEmptyConstructor Document empty constructor 3 64–66
CommentRequired Public method and constructor comments are required 3 68–80
CommentRequired Public method and constructor comments are required 3 82–85
CommentRequired Public method and constructor comments are required 3 87–90
CommentRequired Public method and constructor comments are required 3 92–95
CommentRequired Public method and constructor comments are required 3 97–100
CommentRequired Public method and constructor comments are required 3 102–105
CommentRequired Public method and constructor comments are required 3 107–110
CommentRequired Public method and constructor comments are required 3 112–115
CommentRequired Public method and constructor comments are required 3 117–120
CommentRequired Public method and constructor comments are required 3 122–125
CommentRequired Public method and constructor comments are required 3 127–130
CommentRequired Public method and constructor comments are required 3 132–135
CommentRequired Public method and constructor comments are required 3 137–140
CommentRequired Public method and constructor comments are required 3 142–145
CommentRequired Public method and constructor comments are required 3 147–150
CommentRequired Public method and constructor comments are required 3 152–155
CommentRequired Public method and constructor comments are required 3 157–160
CommentRequired Public method and constructor comments are required 3 162–165
CommentRequired Public method and constructor comments are required 3 167–170

fr/paris/lutece/plugins/appointment/modules/rest/pojo/SolrAppointmentSlotPOJO.java

Rule Violation Priority Line
ClassWithOnlyPrivateConstructorsShouldBeFinal A class which only has private constructors should be final 1 38–150
CommentRequired Header comments are required 3 38–150
DefaultPackage Use explicit scoping instead of the default package private level 3 50–51
CommentDefaultAccessModifier To avoid mistakes add a comment at the beginning of the _strUidFormString field if you want a default access modifier 3 51
DefaultPackage Use explicit scoping instead of the default package private level 3 52–53
CommentDefaultAccessModifier To avoid mistakes add a comment at the beginning of the _strDate field if you want a default access modifier 3 53
DefaultPackage Use explicit scoping instead of the default package private level 3 54–55
CommentDefaultAccessModifier To avoid mistakes add a comment at the beginning of the _strUrl field if you want a default access modifier 3 55
DefaultPackage Use explicit scoping instead of the default package private level 3 56–57
CommentDefaultAccessModifier To avoid mistakes add a comment at the beginning of the _strDayOpen field if you want a default access modifier 3 57
DefaultPackage Use explicit scoping instead of the default package private level 3 58–59
CommentDefaultAccessModifier To avoid mistakes add a comment at the beginning of the _strEnabled field if you want a default access modifier 3 59
DefaultPackage Use explicit scoping instead of the default package private level 3 60–61
CommentDefaultAccessModifier To avoid mistakes add a comment at the beginning of the _strAppointmentActive field if you want a default access modifier 3 61
DefaultPackage Use explicit scoping instead of the default package private level 3 62–63
CommentDefaultAccessModifier To avoid mistakes add a comment at the beginning of the _lNbConsecutivesSlots field if you want a default access modifier 3 63
DefaultPackage Use explicit scoping instead of the default package private level 3 64–65
CommentDefaultAccessModifier To avoid mistakes add a comment at the beginning of the _lMaxConsecutivesSlots field if you want a default access modifier 3 65
CommentRequired Public method and constructor comments are required 3 71–74
CommentRequired Public method and constructor comments are required 3 76–79
CommentRequired Public method and constructor comments are required 3 81–84
CommentRequired Public method and constructor comments are required 3 86–89
CommentRequired Public method and constructor comments are required 3 91–94
CommentRequired Public method and constructor comments are required 3 96–99
CommentRequired Public method and constructor comments are required 3 101–104
CommentRequired Public method and constructor comments are required 3 106–109
CommentRequired Public method and constructor comments are required 3 111–114
CommentRequired Public method and constructor comments are required 3 116–119
CommentRequired Public method and constructor comments are required 3 121–124
CommentRequired Public method and constructor comments are required 3 126–129
CommentRequired Public method and constructor comments are required 3 131–134
CommentRequired Public method and constructor comments are required 3 136–139
CommentRequired Public method and constructor comments are required 3 146–149

fr/paris/lutece/plugins/appointment/modules/rest/pojo/SolrMeetingPointPOJO.java

Rule Violation Priority Line
CommentRequired Header comments are required 3 40–110
DefaultPackage Use explicit scoping instead of the default package private level 3 50–51
CommentDefaultAccessModifier To avoid mistakes add a comment at the beginning of the _strUid field if you want a default access modifier 3 51
DefaultPackage Use explicit scoping instead of the default package private level 3 52–53
CommentDefaultAccessModifier To avoid mistakes add a comment at the beginning of the _strTitle field if you want a default access modifier 3 53
DefaultPackage Use explicit scoping instead of the default package private level 3 54–55
CommentDefaultAccessModifier To avoid mistakes add a comment at the beginning of the _strAddressText field if you want a default access modifier 3 55
DefaultPackage Use explicit scoping instead of the default package private level 3 56–57
CommentDefaultAccessModifier To avoid mistakes add a comment at the beginning of the _strGeoloc field if you want a default access modifier 3 57
DefaultPackage Use explicit scoping instead of the default package private level 3 58–59
CommentDefaultAccessModifier To avoid mistakes add a comment at the beginning of the _strIconUrl field if you want a default access modifier 3 59
CommentRequired Public method and constructor comments are required 3 61–64
CommentRequired Public method and constructor comments are required 3 66–69
CommentRequired Public method and constructor comments are required 3 71–74
CommentRequired Public method and constructor comments are required 3 76–79
CommentRequired Public method and constructor comments are required 3 81–84
CommentRequired Public method and constructor comments are required 3 86–89
CommentRequired Public method and constructor comments are required 3 91–94
CommentRequired Public method and constructor comments are required 3 96–99
CommentRequired Public method and constructor comments are required 3 101–104
CommentRequired Public method and constructor comments are required 3 106–109

fr/paris/lutece/plugins/appointment/modules/rest/pojo/SolrResponseMeetingPointPOJO.java

Rule Violation Priority Line
CommentRequired Header comments are required 3 41–142
CommentRequired Header comments are required 3 58–73
CommentRequired Header comments are required 3 76–92
CommentRequired Header comments are required 3 95–123
DataClass The class 'Group' is suspected to be a Data Class (WOC=0.000%, NOPA=0, NOAM=4, WMC=4) 3 95–123
CommentRequired Header comments are required 3 126–141

fr/paris/lutece/plugins/appointment/modules/rest/rs/AppointmentRest.java

Rule Violation Priority Line
CommentRequired Header comments are required 3 64–133
DefaultPackage Use explicit scoping instead of the default package private level 3 70–71
CommentDefaultAccessModifier To avoid mistakes add a comment at the beginning of the _appointmentRestService field if you want a default access modifier 3 71
UseObjectForClearerAPI Rather than using a lot of String arguments, consider using a container object for those values. 3 76–81
CommentRequired Public method and constructor comments are required 3 76–108
UnnecessaryAnnotationValueElement Avoid the use of value in annotations when its the only element 3 77
UnnecessaryAnnotationValueElement Avoid the use of value in annotations when its the only element 3 78
UnnecessaryAnnotationValueElement Avoid the use of value in annotations when its the only element 3 79
UnnecessaryAnnotationValueElement Avoid the use of value in annotations when its the only element 3 80
UnnecessaryAnnotationValueElement Avoid the use of value in annotations when its the only element 3 81
PreserveStackTrace New exception is thrown in catch block, original stack trace may be lost 3 99–100
PreserveStackTrace New exception is thrown in catch block, original stack trace may be lost 3 104–105
CommentRequired Public method and constructor comments are required 3 114–132
PreserveStackTrace New exception is thrown in catch block, original stack trace may be lost 3 123–124
PreserveStackTrace New exception is thrown in catch block, original stack trace may be lost 3 128–129

fr/paris/lutece/plugins/appointment/modules/rest/rs/filter/QueryParamValidator.java

Rule Violation Priority Line
CommentRequired Header comments are required 3 44–106
ClassNamingConventions The utility class name 'QueryParamValidator' doesn't match '[A-Z][a-zA-Z0-9]+(Utils?|Helper|Home|Service)' 1 44–106
ClassWithOnlyPrivateConstructorsShouldBeFinal A class which only has private constructors should be final 1 44–106
CommentRequired Public method and constructor comments are required 3 58–92
ConfusingTernary Avoid if (x != y) ..; else ..; 3 69–79
ConfusingTernary Avoid if (x != y) ..; else ..; 3 80–90
CommentRequired Public method and constructor comments are required 3 94–105

fr/paris/lutece/plugins/appointment/modules/rest/rs/filter/ValidationErrorResponse.java

Rule Violation Priority Line
CommentRequired Header comments are required 3 39–108
ShortVariable Avoid variables with short names like d 3 53
CommentRequired Public method and constructor comments are required 3 53–56
CommentRequired Header comments are required 3 58–107
DataClass The class 'Detail' is suspected to be a Data Class (WOC=0.000%, NOPA=0, NOAM=6, WMC=8) 3 58–107
CommentDefaultAccessModifier To avoid mistakes add a comment at the beginning of the Detail nested class if you want a default access modifier 3 58–107
CommentRequired Public method and constructor comments are required 3 64–69
CommentRequired Public method and constructor comments are required 3 71–76

fr/paris/lutece/plugins/appointment/modules/rest/service/AppointmentMeetingPointsService.java

Rule Violation Priority Line
UnusedImports Avoid unused imports such as 'com.fasterxml.jackson.core.JsonProcessingException' 4 36
CommentRequired Header comments are required 3 54–165
CommentRequired Public method and constructor comments are required 3 64–73
AvoidSynchronizedAtMethodLevel Use block level rather than method level synchronization 3 64–73
AvoidSynchronizedAtMethodLevel Use block level rather than method level synchronization 3 75–84
CommentRequired Public method and constructor comments are required 3 86–119
CommentRequired Public method and constructor comments are required 3 121–163

fr/paris/lutece/plugins/appointment/modules/rest/service/AppointmentRestService.java

Rule Violation Priority Line
CommentRequired Header comments are required 3 45–62

fr/paris/lutece/plugins/appointment/modules/rest/service/AppointmentSlotsService.java

Rule Violation Priority Line
ClassWithOnlyPrivateConstructorsShouldBeFinal A class which only has private constructors should be final 1 61–153
CommentRequired Header comments are required 3 61–153
CommentRequired Public method and constructor comments are required 3 74–84
AvoidSynchronizedAtMethodLevel Use block level rather than method level synchronization 3 74–84
AvoidSynchronizedAtMethodLevel Use block level rather than method level synchronization 3 86–93
CommentRequired Public method and constructor comments are required 3 95–117
CommentRequired Public method and constructor comments are required 3 125–135

fr/paris/lutece/plugins/appointment/modules/rest/service/IAppointmentRestService.java

Rule Violation Priority Line
CommentRequired Header comments are required 3 45–50
UnnecessaryModifier Unnecessary modifier 'public' on method 'getAvailableTimeSlots': the method is declared in an interface type 3 47
CommentRequired Public method and constructor comments are required 3 47
CommentRequired Public method and constructor comments are required 3 49
UnnecessaryModifier Unnecessary modifier 'public' on method 'getManagedMeetingPoints': the method is declared in an interface type 3 49

fr/paris/lutece/plugins/appointment/modules/rest/util/contsants/AppointmentRestConstants.java

Rule Violation Priority Line
CommentRequired Header comments are required 3 38–89
ClassWithOnlyPrivateConstructorsShouldBeFinal A class which only has private constructors should be final 1 38–89
ClassNamingConventions The utility class name 'AppointmentRestConstants' doesn't match '[A-Z][a-zA-Z0-9]+(Utils?|Helper|Home|Service)' 1 38–89