PMD Results
The following document contains the results of PMD
Files
org/tmforum/mtosi/simulator/client/jaxrpc/axis13/MtosiClientImpl.java
| Violation | Line |
|---|
| Each class should declare at least one constructor | 65 |
| Assigning an Object to null is a code smell. Consider refactoring. | 130 |
org/tmforum/mtosi/simulator/client/MtosiClient.java
| Violation | Line |
|---|
| Each class should declare at least one constructor | 52 |
| A method should have only one exit point, and that should be the last statement in the method | 129 |
| A method should have only one exit point, and that should be the last statement in the method | 133 |
| Avoid instantiating Boolean objects; you can usually invoke Boolean.TRUE instead. | 136 |
| A method should have only one exit point, and that should be the last statement in the method | 144 |
| A method should have only one exit point, and that should be the last statement in the method | 148 |
| A method should have only one exit point, and that should be the last statement in the method | 159 |
org/tmforum/mtosi/simulator/client/MtosiClientFactory.java
| Violation | Line |
|---|
| Each class should declare at least one constructor | 50 |
| A method should have only one exit point, and that should be the last statement in the method | 64 |
org/tmforum/mtosi/simulator/engine/Actions.java
| Violation | Line |
|---|
| It is a good practice to call super() in a constructor | 47 |
org/tmforum/mtosi/simulator/engine/Notification.java
| Violation | Line |
|---|
| It is a good practice to call super() in a constructor | 47 |
org/tmforum/mtosi/simulator/engine/PropertyFileSimulatorEngine.java
| Violation | Line |
|---|
| It is a good practice to call super() in a constructor | 69 |
| It is a good practice to call super() in a constructor | 72 |
| A method should have only one exit point, and that should be the last statement in the method | 122 |
| A method should have only one exit point, and that should be the last statement in the method | 152 |
org/tmforum/mtosi/simulator/engine/Request.java
| Violation | Line |
|---|
| It is a good practice to call super() in a constructor | 53 |
| It is a good practice to call super() in a constructor | 57 |
| Unnecessary final modifier in final class | 69 |
| Unnecessary final modifier in final class | 78 |
| Unnecessary final modifier in final class | 87 |
| Unnecessary final modifier in final class | 96 |
| Unnecessary final modifier in final class | 107 |
| Unnecessary final modifier in final class | 118 |
| Unnecessary final modifier in final class | 129 |
| Unnecessary final modifier in final class | 140 |
org/tmforum/mtosi/simulator/engine/Response.java
| Violation | Line |
|---|
| It is a good practice to call super() in a constructor | 39 |
org/tmforum/mtosi/simulator/engine/ServerActions.java
| Violation | Line |
|---|
| Each class should declare at least one constructor | 34 |
org/tmforum/mtosi/simulator/engine/SimulatorEngine.java
| Violation | Line |
|---|
| Avoid modifiers which are implied by the context | 53 |
| Avoid modifiers which are implied by the context | 68 |
| Avoid modifiers which are implied by the context | 83 |
org/tmforum/mtosi/simulator/server/jaxrpc/axis13/Axis13Server.java
| Violation | Line |
|---|
| It is a good practice to call super() in a constructor | 109 |
| Avoid unnecessary temporaries when converting primitives to Strings | 227 |
| Avoid empty catch blocks | 234 |
| Assigning an Object to null is a code smell. Consider refactoring. | 341 |
| Assigning an Object to null is a code smell. Consider refactoring. | 351 |
| A method should have only one exit point, and that should be the last statement in the method | 364 |
org/tmforum/mtosi/simulator/server/jaxrpc/axis13/Axis13Worker.java
| Violation | Line |
|---|
| It is a good practice to call super() in a constructor | 145 |
| Assigning an Object to null is a code smell. Consider refactoring. | 198 |
| A method should have only one exit point, and that should be the last statement in the method | 309 |
| A method should have only one exit point, and that should be the last statement in the method | 341 |
| Avoid empty catch blocks | 466 |
| Avoid empty catch blocks | 524 |
| Avoid empty catch blocks | 531 |
| A method should have only one exit point, and that should be the last statement in the method | 591 |
| Avoid assigments in operands | 605 |
| A method should have only one exit point, and that should be the last statement in the method | 708 |
| A method should have only one exit point, and that should be the last statement in the method | 721 |
| Avoid assigments in operands | 772 |
org/tmforum/mtosi/simulator/server/jaxrpc/axis13/HTTPConstants.java
| Violation | Line |
|---|
| Each class should declare at least one constructor | 26 |
org/tmforum/mtosi/simulator/server/jaxrpc/axis13/MtosiServerImpl.java
| Violation | Line |
|---|
| Avoid unnecessary constructors - the compiler will generate these for you | 79 |
| It is a good practice to call super() in a constructor | 79 |
| A method should have only one exit point, and that should be the last statement in the method | 89 |
| Assigning an Object to null is a code smell. Consider refactoring. | 151 |
| Assigning an Object to null is a code smell. Consider refactoring. | 157 |
org/tmforum/mtosi/simulator/server/jaxrpc/axis13/NonBlockingBufferedInputStream.java
| Violation | Line |
|---|
| Each class should declare at least one constructor | 22 |
| A method should have only one exit point, and that should be the last statement in the method | 85 |
| A method should have only one exit point, and that should be the last statement in the method | 87 |
| A method should have only one exit point, and that should be the last statement in the method | 120 |
| A method should have only one exit point, and that should be the last statement in the method | 124 |
| A method should have only one exit point, and that should be the last statement in the method | 126 |
| A method should have only one exit point, and that should be the last statement in the method | 128 |
| A method should have only one exit point, and that should be the last statement in the method | 150 |
| A method should have only one exit point, and that should be the last statement in the method | 170 |
| A method should have only one exit point, and that should be the last statement in the method | 172 |
org/tmforum/mtosi/simulator/server/MtosiServer.java
| Violation | Line |
|---|
| Each class should declare at least one constructor | 52 |
| A method should have only one exit point, and that should be the last statement in the method | 103 |
| A method should have only one exit point, and that should be the last statement in the method | 107 |
| Avoid instantiating Boolean objects; you can usually invoke Boolean.TRUE instead. | 110 |
| A method should have only one exit point, and that should be the last statement in the method | 118 |
| A method should have only one exit point, and that should be the last statement in the method | 122 |
| A method should have only one exit point, and that should be the last statement in the method | 133 |
org/tmforum/mtosi/simulator/server/MtosiServerFactory.java
| Violation | Line |
|---|
| Each class should declare at least one constructor | 51 |
| A method should have only one exit point, and that should be the last statement in the method | 65 |
org/tmforum/mtosi/simulator/services/jaxrpc/axis13/AlarmRetrievalSoapHTTPBinding.java
| Violation | Line |
|---|
| It is a good practice to call super() in a constructor | 64 |
org/tmforum/mtosi/simulator/services/jaxrpc/axis13/DiscoveryServiceSoapHTTPBinding.java
| Violation | Line |
|---|
| It is a good practice to call super() in a constructor | 62 |
org/tmforum/mtosi/simulator/services/jaxrpc/axis13/EquipmentInventoryMgrSoapHTTPBinding.java
| Violation | Line |
|---|
| It is a good practice to call super() in a constructor | 70 |
org/tmforum/mtosi/simulator/services/jaxrpc/axis13/InventoryRetrievalSoapHTTPBinding.java
| Violation | Line |
|---|
| It is a good practice to call super() in a constructor | 64 |
org/tmforum/mtosi/simulator/services/jaxrpc/axis13/ManagedElementMgrSoapHTTPBinding.java
| Violation | Line |
|---|
| It is a good practice to call super() in a constructor | 78 |
org/tmforum/mtosi/simulator/services/jaxrpc/axis13/MultiLayerSubnetworkMgrSoapHTTPBinding.java
| Violation | Line |
|---|
| It is a good practice to call super() in a constructor | 78 |
org/tmforum/mtosi/simulator/services/jaxrpc/axis13/NotificationBrokerSoapHTTPBinding.java
| Violation | Line |
|---|
| It is a good practice to call super() in a constructor | 64 |
org/tmforum/mtosi/simulator/services/jaxrpc/axis13/NotificationConsumerSoapHTTPBinding.java
| Violation | Line |
|---|
| It is a good practice to call super() in a constructor | 61 |
org/tmforum/mtosi/simulator/services/jaxrpc/axis13/OperationsSystemsMgrSoapHTTPBinding.java
| Violation | Line |
|---|
| It is a good practice to call super() in a constructor | 77 |
org/tmforum/mtosi/simulator/services/jaxrpc/axis13/ProtectionMgrSoapHTTPBinding.java
| Violation | Line |
|---|
| It is a good practice to call super() in a constructor | 69 |
org/tmforum/mtosi/simulator/services/jaxrpc/axis13/TransmissionDescriptorMgrSoapHTTPBinding.java
| Violation | Line |
|---|
| It is a good practice to call super() in a constructor | 66 |
org/tmforum/mtosi/simulator/services/jaxrpc/axis13/Util.java
| Violation | Line |
|---|
| It is a good practice to call super() in a constructor | 67 |
| It is a good practice to call super() in a constructor | 70 |
| A method should have only one exit point, and that should be the last statement in the method | 96 |
org/tmforum/mtosi/simulator/Simulator.java
| Violation | Line |
|---|
| Each class should declare at least one constructor | 54 |
| Assigning an Object to null is a code smell. Consider refactoring. | 314 |
| Assigning an Object to null is a code smell. Consider refactoring. | 332 |
org/tmforum/mtosi/simulator/util/Actor.java
| Violation | Line |
|---|
| It is a good practice to call super() in a constructor | 72 |
org/tmforum/mtosi/simulator/util/ActorFactory.java
| Violation | Line |
|---|
| It is a good practice to call super() in a constructor | 60 |
org/tmforum/mtosi/simulator/util/EndPoint.java
| Violation | Line |
|---|
| Each class should declare at least one constructor | 40 |
org/tmforum/mtosi/simulator/util/jaxrpc/axis13/Deserialization.java
| Violation | Line |
|---|
| It is a good practice to call super() in a constructor | 60 |
org/tmforum/mtosi/simulator/util/jaxrpc/axis13/MtosiMessageParserImpl.java
| Violation | Line |
|---|
| Each class should declare at least one constructor | 61 |
org/tmforum/mtosi/simulator/util/jaxrpc/axis13/Serialization.java
| Violation | Line |
|---|
| Perhaps '_javaClass' could be replaced by a local variable. | 53 |
| It is a good practice to call super() in a constructor | 56 |
org/tmforum/mtosi/simulator/util/Message.java
| Violation | Line |
|---|
| It is a good practice to call super() in a constructor | 90 |
org/tmforum/mtosi/simulator/util/MessageConstants.java
| Violation | Line |
|---|
| Each class should declare at least one constructor | 40 |
org/tmforum/mtosi/simulator/util/MessageListener.java
| Violation | Line |
|---|
| Avoid modifiers which are implied by the context | 46 |
org/tmforum/mtosi/simulator/util/Messages.java
| Violation | Line |
|---|
| It is a good practice to call super() in a constructor | 67 |
| It is a good practice to call super() in a constructor | 71 |
| A method should have only one exit point, and that should be the last statement in the method | 77 |
| A method should have only one exit point, and that should be the last statement in the method | 95 |
org/tmforum/mtosi/simulator/util/MessagesFactory.java
| Violation | Line |
|---|
| Each class should declare at least one constructor | 43 |
org/tmforum/mtosi/simulator/util/MtosiMessage.java
| Violation | Line |
|---|
| It is a good practice to call super() in a constructor | 46 |
org/tmforum/mtosi/simulator/util/MtosiMessageParser.java
| Violation | Line |
|---|
| It is a good practice to call super() in a constructor | 77 |
org/tmforum/mtosi/simulator/util/MtosiMessageParserFactory.java
| Violation | Line |
|---|
| Unnecessary final modifier in final class | 71 |
| Avoid empty if statements | 76 |
| Unnecessary final modifier in final class | 95 |
org/tmforum/mtosi/simulator/util/Resources.java
| Violation | Line |
|---|
| It is a good practice to call super() in a constructor | 58 |
| Double checked locking is not thread safe in Java. | 66 |
| Unnecessary final modifier in final class | 66 |
org/tmforum/mtosi/simulator/util/Runner.java
| Violation | Line |
|---|
| It is a good practice to call super() in a constructor | 70 |
| It is a good practice to call super() in a constructor | 81 |
org/tmforum/mtosi/simulator/util/Simulator.java
| Violation | Line |
|---|
| It is a good practice to call super() in a constructor | 82 |
| Assigning an Object to null is a code smell. Consider refactoring. | 197 |
org/tmforum/mtosi/simulator/util/UseCase.java
| Violation | Line |
|---|
| It is a good practice to call super() in a constructor | 101 |
org/tmforum/mtosi/simulator/util/Util.java
| Violation | Line |
|---|
| Each class should declare at least one constructor | 45 |
| A method should have only one exit point, and that should be the last statement in the method | 62 |
| A method should have only one exit point, and that should be the last statement in the method | 78 |
| A method should have only one exit point, and that should be the last statement in the method | 86 |
