##### Documentation

- Introduction
- Download
- How to develop ?
- XML configuration

##### Demo

- Flex Examples
- AS3 Example
- Examples source code

##### API documentation

- Core AsDocs
- Flex components
- Flex AsDocs
- Proj4as AsDocs

##### Useful links

- OpenScales homepage
- Discussion group
- Bugtracker

##### Project Documentation

- Project Information
- Project Reports
  - Flex PMD Report
  - Surefire Report

## Flex PMD Report

PMD 4.2.2.

## Files

### AbstractDrawHandler.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1

### AbstractEditCollectionHandler.as

Violation | Line
--- | ---
A high number of imports can indicate a high degree of coupling within an object. (15 maximum but 17 actually). A high number of imports can indicate a high degree of coupling within an object. Rule counts the number of unique imports and reports a violation if the count is above the user defined threshold. | -1
A high number of imports can indicate a high degree of coupling within an object. (15 maximum but 17 actually). A high number of imports can indicate a high degree of coupling within an object. Rule counts the number of unique imports and reports a violation if the count is above the user defined threshold. | -1
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
Too many methods detected (10 maximum, but 11 actually). A class with too many methods is probably a good suspect for refactoring, in order to reduce its complexity and find a way to have more fine grained objects. | 28
Too many methods detected (10 maximum, but 11 actually). A class with too many methods is probably a good suspect for refactoring, in order to reduce its complexity and find a way to have more fine grained objects. | 28
If this field (_pointUnderTheMouse) was meant to be a constant, make it constant. Otherwise, if it is used as a global variable, you may want to redesign this class | 39
If this field (_pointUnderTheMouse) was meant to be a constant, make it constant. Otherwise, if it is used as a global variable, you may want to redesign this class | 39
Long parameter list detected (4 maximum, but 6 actually). Long parameter lists can indicate that a new object should be created to wrap the numerous parameters. Basically, try to group the parameters together. | 57
Long parameter list detected (4 maximum, but 6 actually). Long parameter lists can indicate that a new object should be created to wrap the numerous parameters. Basically, try to group the parameters together. | 57
Too long line (200 maximum, but 211 actually). | 57
Too long line (200 maximum, but 211 actually). | 57
Nested if statements are not a good design | 115
Nested if statements are not a good design | 115
Nested if statements are not a good design | 115
Nested if statements are not a good design | 115
This variable (geom) is not used. | 146
This variable (geom) is not used. | 146
This method is too complex. Maximum complexity is 10, but its cyclomatic complexity was 12 | 221
This method is too complex. Maximum complexity is 10, but its cyclomatic complexity was 12 | 221
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 226
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 226
This variable (tmpPx) seems to be incorrectly named. Let your creativity flow | 230
This variable (tmpPx) seems to be incorrectly named. Let your creativity flow | 230
Instanciating a variable in a loop can be expensive. | 230
Instanciating a variable in a loop can be expensive. | 230
Nested if statements are not a good design | 241
Nested if statements are not a good design | 241
Nested if statements are not a good design | 241
Nested if statements are not a good design | 241
Nested if statements are not a good design | 247
Nested if statements are not a good design | 247
Nested if statements are not a good design | 251
Nested if statements are not a good design | 251
Nested if statements are not a good design | 251
Nested if statements are not a good design | 251
Nested if statements are not a good design | 259
Nested if statements are not a good design | 259
Nested if statements are not a good design | 288
Nested if statements are not a good design | 288

### AbstractEditHandler.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
Constructor must be as lightweight as possible. No control statement allowed, whereas a cyclomatic complexe of 2 has been detected. The Just-In-Time compiler does not compile constructors. Make them as lightweight as possible, or move the complexity of the code to a method called by the constructor. Then the complexity will be compiled by the JIT. | 64
Constructor must be as lightweight as possible. No control statement allowed, whereas a cyclomatic complexe of 2 has been detected. The Just-In-Time compiler does not compile constructors. Make them as lightweight as possible, or move the complexity of the code to a method called by the constructor. Then the complexity will be compiled by the JIT. | 64
Long parameter list detected (4 maximum, but 6 actually). Long parameter lists can indicate that a new object should be created to wrap the numerous parameters. Basically, try to group the parameters together. | 64
Long parameter list detected (4 maximum, but 6 actually). Long parameter lists can indicate that a new object should be created to wrap the numerous parameters. Basically, try to group the parameters together. | 64
Too long line (200 maximum, but 203 actually). | 64
Too long line (200 maximum, but 203 actually). | 64
Flex specific - You must add child only inside the createChildren method | 179
Flex specific - You must add child only inside the createChildren method | 179
This parameter (vectorfeature) of this function is not used. | 187
This parameter (vectorfeature) of this function is not used. | 187
This parameter (vectorfeature) of this function is not used. | 194
This parameter (vectorfeature) of this function is not used. | 194
This variable (tmpfeature) seems to be incorrectly named. Let your creativity flow | 227
This variable (tmpfeature) seems to be incorrectly named. Let your creativity flow | 227

### AbstractParams.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
This parameter (key) of this function is not used. | 23
This parameter (key) of this function is not used. | 23
This parameter (value) of this function is not used. | 23
This parameter (value) of this function is not used. | 23

### AbstractRequest.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1

### AbstractSecurity.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 58
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 58

### Anchored.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
Too many field detected (5 maximum, but 6 actually). Classes that have too many fields could be redesigned to have fewer fields, possibly through some nested object grouping of some of the information. For example, a class with city/state/zipcode fields could instead have one Address field. | 14
Too many field detected (5 maximum, but 6 actually). Classes that have too many fields could be redesigned to have fewer fields, possibly through some nested object grouping of some of the information. For example, a class with city/state/zipcode fields could instead have one Address field. | 14
If this field (BR) was meant to be a constant, make it constant. Otherwise, if it is used as a global variable, you may want to redesign this class | 22
If this field (BR) was meant to be a constant, make it constant. Otherwise, if it is used as a global variable, you may want to redesign this class | 22
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 22
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 22
If this field (TR) was meant to be a constant, make it constant. Otherwise, if it is used as a global variable, you may want to redesign this class | 23
If this field (TR) was meant to be a constant, make it constant. Otherwise, if it is used as a global variable, you may want to redesign this class | 23
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 23
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 23
If this field (TL) was meant to be a constant, make it constant. Otherwise, if it is used as a global variable, you may want to redesign this class | 24
If this field (TL) was meant to be a constant, make it constant. Otherwise, if it is used as a global variable, you may want to redesign this class | 24
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 24
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 24
If this field (BL) was meant to be a constant, make it constant. Otherwise, if it is used as a global variable, you may want to redesign this class | 25
If this field (BL) was meant to be a constant, make it constant. Otherwise, if it is used as a global variable, you may want to redesign this class | 25
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 25
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 25
Long parameter list detected (4 maximum, but 7 actually). Long parameter lists can indicate that a new object should be created to wrap the numerous parameters. Basically, try to group the parameters together. | 29
Long parameter list detected (4 maximum, but 7 actually). Long parameter lists can indicate that a new object should be created to wrap the numerous parameters. Basically, try to group the parameters together. | 29
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 64
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 64

### Arrow.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
Embed metadata detected in source code where a stylesheet may be cleaner | 15
Embed metadata detected in source code where a stylesheet may be cleaner | 15
Embed metadata detected in source code where a stylesheet may be cleaner | 18
Embed metadata detected in source code where a stylesheet may be cleaner | 18
Constructor must be as lightweight as possible. No control statement allowed, whereas a cyclomatic complexe of 2 has been detected. The Just-In-Time compiler does not compile constructors. Make them as lightweight as possible, or move the complexity of the code to a method called by the constructor. Then the complexity will be compiled by the JIT. | 24
Constructor must be as lightweight as possible. No control statement allowed, whereas a cyclomatic complexe of 2 has been detected. The Just-In-Time compiler does not compile constructors. Make them as lightweight as possible, or move the complexity of the code to a method called by the constructor. Then the complexity will be compiled by the JIT. | 24
Flex specific - You must add child only inside the createChildren method | 53
Flex specific - You must add child only inside the createChildren method | 53

### BitmapFill.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1

### BorderPanHandler.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1

### Bounds.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
Too many methods detected (10 maximum, but 21 actually). A class with too many methods is probably a good suspect for refactoring, in order to reduce its complexity and find a way to have more fine grained objects. | 16
Too many methods detected (10 maximum, but 21 actually). A class with too many methods is probably a good suspect for refactoring, in order to reduce its complexity and find a way to have more fine grained objects. | 16
Too many public fields or functions detected (10 maximum, but 20 actually). A large number of public methods and attributes declared in a class can indicate the class may need to be broken up as increased effort will be required to thoroughly test it. | 16
Too many public fields or functions detected (10 maximum, but 20 actually). A large number of public methods and attributes declared in a class can indicate the class may need to be broken up as increased effort will be required to thoroughly test it. | 16
Constructor must be as lightweight as possible. No control statement allowed, whereas a cyclomatic complexe of 5 has been detected. The Just-In-Time compiler does not compile constructors. Make them as lightweight as possible, or move the complexity of the code to a method called by the constructor. Then the complexity will be compiled by the JIT. | 31
Constructor must be as lightweight as possible. No control statement allowed, whereas a cyclomatic complexe of 5 has been detected. The Just-In-Time compiler does not compile constructors. Make them as lightweight as possible, or move the complexity of the code to a method called by the constructor. Then the complexity will be compiled by the JIT. | 31
This variable (tempBbox) seems to be incorrectly named. Let your creativity flow | 365
This variable (tempBbox) seems to be incorrectly named. Let your creativity flow | 365
This variable (tempBboxArr) seems to be incorrectly named. Let your creativity flow | 366
This variable (tempBboxArr) seems to be incorrectly named. Let your creativity flow | 366

### Button.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
Constructor must be as lightweight as possible. No control statement allowed, whereas a cyclomatic complexe of 2 has been detected. The Just-In-Time compiler does not compile constructors. Make them as lightweight as possible, or move the complexity of the code to a method called by the constructor. Then the complexity will be compiled by the JIT. | 17
Constructor must be as lightweight as possible. No control statement allowed, whereas a cyclomatic complexe of 2 has been detected. The Just-In-Time compiler does not compile constructors. Make them as lightweight as possible, or move the complexity of the code to a method called by the constructor. Then the complexity will be compiled by the JIT. | 17
Flex specific - You must add child only inside the createChildren method | 26
Flex specific - You must add child only inside the createChildren method | 26

### CapabilitiesParser.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
Too many field detected (5 maximum, but 10 actually). Classes that have too many fields could be redesigned to have fewer fields, possibly through some nested object grouping of some of the information. For example, a class with city/state/zipcode fields could instead have one Address field. | 9
Too many field detected (5 maximum, but 10 actually). Classes that have too many fields could be redesigned to have fewer fields, possibly through some nested object grouping of some of the information. For example, a class with city/state/zipcode fields could instead have one Address field. | 9
This parameter (doc) of this function is not used. | 30
This parameter (doc) of this function is not used. | 30

### CheckBox.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
Embed metadata detected in source code where a stylesheet may be cleaner | 15
Embed metadata detected in source code where a stylesheet may be cleaner | 15
Embed metadata detected in source code where a stylesheet may be cleaner | 18
Embed metadata detected in source code where a stylesheet may be cleaner | 18
This test contains a hard coded boolean value. You could remove it by having '!condition' | 47
This test contains a hard coded boolean value. You could remove it by having '!condition' | 47
Flex specific - You must add child only inside the createChildren method | 52
Flex specific - You must add child only inside the createChildren method | 52

### ClickHandler.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
Too many field detected (5 maximum, but 11 actually). Classes that have too many fields could be redesigned to have fewer fields, possibly through some nested object grouping of some of the information. For example, a class with city/state/zipcode fields could instead have one Address field. | 23
Too many field detected (5 maximum, but 11 actually). Classes that have too many fields could be redesigned to have fewer fields, possibly through some nested object grouping of some of the information. For example, a class with city/state/zipcode fields could instead have one Address field. | 23
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 158
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 158
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 159
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 159

### Collection.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
Too many methods detected (10 maximum, but 15 actually). A class with too many methods is probably a good suspect for refactoring, in order to reduce its complexity and find a way to have more fine grained objects. | 17
Too many methods detected (10 maximum, but 15 actually). A class with too many methods is probably a good suspect for refactoring, in order to reduce its complexity and find a way to have more fine grained objects. | 17
Too many public fields or functions detected (10 maximum, but 15 actually). A large number of public methods and attributes declared in a class can indicate the class may need to be broken up as increased effort will be required to thoroughly test it. | 17
Too many public fields or functions detected (10 maximum, but 15 actually). A large number of public methods and attributes declared in a class can indicate the class may need to be broken up as increased effort will be required to thoroughly test it. | 17
ArrayElementType metadata is not specified for this array-type field (_components). | 22
ArrayElementType metadata is not specified for this array-type field (_components). | 22
ArrayElementType metadata is not specified for this array-type field (_componentTypes). | 29
ArrayElementType metadata is not specified for this array-type field (_componentTypes). | 29
Constructor must be as lightweight as possible. No control statement allowed, whereas a cyclomatic complexe of 2 has been detected. The Just-In-Time compiler does not compile constructors. Make them as lightweight as possible, or move the complexity of the code to a method called by the constructor. Then the complexity will be compiled by the JIT. | 36
Constructor must be as lightweight as possible. No control statement allowed, whereas a cyclomatic complexe of 2 has been detected. The Just-In-Time compiler does not compile constructors. Make them as lightweight as possible, or move the complexity of the code to a method called by the constructor. Then the complexity will be compiled by the JIT. | 36
Nested if statements are not a good design | 190
Nested if statements are not a good design | 190
Nested if statements are not a good design | 190
Nested if statements are not a good design | 190
Using digits at the end of a symbol does not help understanging the meaning of it | 191
Using digits at the end of a symbol does not help understanging the meaning of it | 191
Using digits at the end of a symbol does not help understanging the meaning of it | 192
Using digits at the end of a symbol does not help understanging the meaning of it | 192
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 319
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 319
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 341
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 341

### Configuration.as

Violation | Line
--- | ---
A high number of imports can indicate a high degree of coupling within an object. (15 maximum but 26 actually). A high number of imports can indicate a high degree of coupling within an object. Rule counts the number of unique imports and reports a violation if the count is above the user defined threshold. | -1
A high number of imports can indicate a high degree of coupling within an object. (15 maximum but 26 actually). A high number of imports can indicate a high degree of coupling within an object. Rule counts the number of unique imports and reports a violation if the count is above the user defined threshold. | -1
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
This method is too complex. Maximum complexity is 10, but its cyclomatic complexity was 24 | 190
This method is too complex. Maximum complexity is 10, but its cyclomatic complexity was 24 | 190
This function is far too long (20 maximum, but 42 actually). Violations of this rule usually indicate that the method has too much responsibility. Try to reduce the method size by creating helper methods and removing any copy/pasted code. | 190
This function is far too long (20 maximum, but 42 actually). Violations of this rule usually indicate that the method has too much responsibility. Try to reduce the method size by creating helper methods and removing any copy/pasted code. | 190
This test contains a hard coded boolean value. You could remove it by having 'condition' | 198
This test contains a hard coded boolean value. You could remove it by having 'condition' | 198
This test contains a hard coded boolean value. You could remove it by having '!condition' | 200
This test contains a hard coded boolean value. You could remove it by having '!condition' | 200
This test contains a hard coded boolean value. You could remove it by having 'condition' | 229
This test contains a hard coded boolean value. You could remove it by having 'condition' | 229
This test contains a hard coded boolean value. You could remove it by having 'condition' | 233
This test contains a hard coded boolean value. You could remove it by having 'condition' | 233
There are too few branches in this switch statement (3 minimum, but 2 actual). Switch statements are designed for complex branches, and allow branches to share treatment. Using a switch for only 2 branches is ill advised, as switches are not as easy to understand as if. In this case, it's most likely is a good idea to use a if statement | 244
There are too few branches in this switch statement (3 minimum, but 2 actual). Switch statements are designed for complex branches, and allow branches to share treatment. Using a switch for only 2 branches is ill advised, as switches are not as easy to understand as if. In this case, it's most likely is a good idea to use a if statement | 244
Long switch case detected (3 lines maximum, but 7 actually). A switch case statement should be either empty, or contain a break, or call another method. | 245
Long switch case detected (3 lines maximum, but 7 actually). A switch case statement should be either empty, or contain a break, or call another method. | 245
Long switch case detected (3 lines maximum, but 7 actually). A switch case statement should be either empty, or contain a break, or call another method. | 255
Long switch case detected (3 lines maximum, but 7 actually). A switch case statement should be either empty, or contain a break, or call another method. | 255
This method is too complex. Maximum complexity is 10, but its cyclomatic complexity was 13 | 325
This method is too complex. Maximum complexity is 10, but its cyclomatic complexity was 13 | 325
This test contains a hard coded boolean value. You could remove it by having 'condition' | 329
This test contains a hard coded boolean value. You could remove it by having 'condition' | 329
This statement is empty. | 330
This statement is empty. | 330
This test contains a hard coded boolean value. You could remove it by having 'condition' | 339
This test contains a hard coded boolean value. You could remove it by having 'condition' | 339
Nested if statements are not a good design | 339
Nested if statements are not a good design | 339
Nested if statements are not a good design | 339
Nested if statements are not a good design | 339
This statement is empty. | 340
This statement is empty. | 340
Nested if statements are not a good design | 347
Nested if statements are not a good design | 347
Nested if statements are not a good design | 347
Nested if statements are not a good design | 347
This test contains a hard coded boolean value. You could remove it by having 'condition' | 349
This test contains a hard coded boolean value. You could remove it by having 'condition' | 349
Nested if statements are not a good design | 349
Nested if statements are not a good design | 349
Nested if statements are not a good design | 349
Nested if statements are not a good design | 349
This statement is empty. | 350
This statement is empty. | 350
This function is far too long (20 maximum, but 21 actually). Violations of this rule usually indicate that the method has too much responsibility. Try to reduce the method size by creating helper methods and removing any copy/pasted code. | 363
This function is far too long (20 maximum, but 21 actually). Violations of this rule usually indicate that the method has too much responsibility. Try to reduce the method size by creating helper methods and removing any copy/pasted code. | 363

### ContainsFilter.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1

### Control.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
Constructor must be as lightweight as possible. No control statement allowed, whereas a cyclomatic complexe of 2 has been detected. The Just-In-Time compiler does not compile constructors. Make them as lightweight as possible, or move the complexity of the code to a method called by the constructor. Then the complexity will be compiled by the JIT. | 20
Constructor must be as lightweight as possible. No control statement allowed, whereas a cyclomatic complexe of 2 has been detected. The Just-In-Time compiler does not compile constructors. Make them as lightweight as possible, or move the complexity of the code to a method called by the constructor. Then the complexity will be compiled by the JIT. | 20

### CrosshairCursor.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
Nested if statements are not a good design | 77
Nested if statements are not a good design | 77

### CycleMap.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
Long parameter list detected (4 maximum, but 5 actually). Long parameter lists can indicate that a new object should be created to wrap the numerous parameters. Basically, try to group the parameters together. | 13
Long parameter list detected (4 maximum, but 5 actually). Long parameter lists can indicate that a new object should be created to wrap the numerous parameters. Basically, try to group the parameters together. | 13

### DataRequest.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
Constructor must be as lightweight as possible. No control statement allowed, whereas a cyclomatic complexe of 7 has been detected. The Just-In-Time compiler does not compile constructors. Make them as lightweight as possible, or move the complexity of the code to a method called by the constructor. Then the complexity will be compiled by the JIT. | 33
Constructor must be as lightweight as possible. No control statement allowed, whereas a cyclomatic complexe of 7 has been detected. The Just-In-Time compiler does not compile constructors. Make them as lightweight as possible, or move the complexity of the code to a method called by the constructor. Then the complexity will be compiled by the JIT. | 33
Long parameter list detected (4 maximum, but 5 actually). Long parameter lists can indicate that a new object should be created to wrap the numerous parameters. Basically, try to group the parameters together. | 33
Long parameter list detected (4 maximum, but 5 actually). Long parameter lists can indicate that a new object should be created to wrap the numerous parameters. Basically, try to group the parameters together. | 33
This catch statement is empty | 85
This catch statement is empty | 85
This statement is empty. | 87
This statement is empty. | 87

### DisplayObjectMarker.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 9
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 9
Long parameter list detected (4 maximum, but 6 actually). Long parameter lists can indicate that a new object should be created to wrap the numerous parameters. Basically, try to group the parameters together. | 15
Long parameter list detected (4 maximum, but 6 actually). Long parameter lists can indicate that a new object should be created to wrap the numerous parameters. Basically, try to group the parameters together. | 15

### DragFeatureHandler.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
ArrayElementType metadata is not specified for this array-type field (_undraggableFeatures). | 28
ArrayElementType metadata is not specified for this array-type field (_undraggableFeatures). | 28
ArrayElementType metadata is not specified for this array-type field (_draggableLayers). | 32
ArrayElementType metadata is not specified for this array-type field (_draggableLayers). | 32
Nested if statements are not a good design | 93
Nested if statements are not a good design | 93

### DragHandler.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
Too many field detected (5 maximum, but 6 actually). Classes that have too many fields could be redesigned to have fewer fields, possibly through some nested object grouping of some of the information. For example, a class with city/state/zipcode fields could instead have one Address field. | 20
Too many field detected (5 maximum, but 6 actually). Classes that have too many fields could be redesigned to have fewer fields, possibly through some nested object grouping of some of the information. For example, a class with city/state/zipcode fields could instead have one Address field. | 20

### DraggableSprite.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1

### DrawHandler.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
Too many public fields or functions detected (10 maximum, but 13 actually). A large number of public methods and attributes declared in a class can indicate the class may need to be broken up as increased effort will be required to thoroughly test it. | 19
Too many public fields or functions detected (10 maximum, but 13 actually). A large number of public methods and attributes declared in a class can indicate the class may need to be broken up as increased effort will be required to thoroughly test it. | 19
Too many field detected (5 maximum, but 10 actually). Classes that have too many fields could be redesigned to have fewer fields, possibly through some nested object grouping of some of the information. For example, a class with city/state/zipcode fields could instead have one Address field. | 19
Too many field detected (5 maximum, but 10 actually). Classes that have too many fields could be redesigned to have fewer fields, possibly through some nested object grouping of some of the information. For example, a class with city/state/zipcode fields could instead have one Address field. | 19
Constructor must be as lightweight as possible. No control statement allowed, whereas a cyclomatic complexe of 2 has been detected. The Just-In-Time compiler does not compile constructors. Make them as lightweight as possible, or move the complexity of the code to a method called by the constructor. Then the complexity will be compiled by the JIT. | 79
Constructor must be as lightweight as possible. No control statement allowed, whereas a cyclomatic complexe of 2 has been detected. The Just-In-Time compiler does not compile constructors. Make them as lightweight as possible, or move the complexity of the code to a method called by the constructor. Then the complexity will be compiled by the JIT. | 79
This private method (onSelectionUpdated) is used but its content is empty. | 90
This private method (onSelectionUpdated) is used but its content is empty. | 90
This private method (deleteAllFeatures) does not seem to be used. | 94
This private method (deleteAllFeatures) does not seem to be used. | 94
There are too few branches in this switch statement (3 minimum, but 2 actual). Switch statements are designed for complex branches, and allow branches to share treatment. Using a switch for only 2 branches is ill advised, as switches are not as easy to understand as if. In this case, it's most likely is a good idea to use a if statement | 104
There are too few branches in this switch statement (3 minimum, but 2 actual). Switch statements are designed for complex branches, and allow branches to share treatment. Using a switch for only 2 branches is ill advised, as switches are not as easy to understand as if. In this case, it's most likely is a good idea to use a if statement | 104
This method is too complex. Maximum complexity is 10, but its cyclomatic complexity was 21 | 165
This method is too complex. Maximum complexity is 10, but its cyclomatic complexity was 21 | 165
This function is far too long (20 maximum, but 57 actually). Violations of this rule usually indicate that the method has too much responsibility. Try to reduce the method size by creating helper methods and removing any copy/pasted code. | 165
This function is far too long (20 maximum, but 57 actually). Violations of this rule usually indicate that the method has too much responsibility. Try to reduce the method size by creating helper methods and removing any copy/pasted code. | 165
Long switch case detected (3 lines maximum, but 11 actually). A switch case statement should be either empty, or contain a break, or call another method. | 168
Long switch case detected (3 lines maximum, but 11 actually). A switch case statement should be either empty, or contain a break, or call another method. | 168
Long switch case detected (3 lines maximum, but 11 actually). A switch case statement should be either empty, or contain a break, or call another method. | 181
Long switch case detected (3 lines maximum, but 11 actually). A switch case statement should be either empty, or contain a break, or call another method. | 181
Long switch case detected (3 lines maximum, but 13 actually). A switch case statement should be either empty, or contain a break, or call another method. | 195
Long switch case detected (3 lines maximum, but 13 actually). A switch case statement should be either empty, or contain a break, or call another method. | 195
Long switch case detected (3 lines maximum, but 13 actually). A switch case statement should be either empty, or contain a break, or call another method. | 211
Long switch case detected (3 lines maximum, but 13 actually). A switch case statement should be either empty, or contain a break, or call another method. | 211
Long switch case detected (3 lines maximum, but 12 actually). A switch case statement should be either empty, or contain a break, or call another method. | 227
Long switch case detected (3 lines maximum, but 12 actually). A switch case statement should be either empty, or contain a break, or call another method. | 227
Long switch case detected (3 lines maximum, but 14 actually). A switch case statement should be either empty, or contain a break, or call another method. | 241
Long switch case detected (3 lines maximum, but 14 actually). A switch case statement should be either empty, or contain a break, or call another method. | 241
This method is too complex. Maximum complexity is 10, but its cyclomatic complexity was 11 | 262
This method is too complex. Maximum complexity is 10, but its cyclomatic complexity was 11 | 262
This function is far too long (20 maximum, but 22 actually). Violations of this rule usually indicate that the method has too much responsibility. Try to reduce the method size by creating helper methods and removing any copy/pasted code. | 262
This function is far too long (20 maximum, but 22 actually). Violations of this rule usually indicate that the method has too much responsibility. Try to reduce the method size by creating helper methods and removing any copy/pasted code. | 262
This variable (lastFeature) is not used. | 264
This variable (lastFeature) is not used. | 264
Nested if statements are not a good design | 274
Nested if statements are not a good design | 274
Nested if statements are not a good design | 274
Nested if statements are not a good design | 274
Nested if statements are not a good design | 276
Nested if statements are not a good design | 276
Nested if statements are not a good design | 276
Nested if statements are not a good design | 276

### DrawMultiHandler.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 34
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 34
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 61
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 61

### DrawPathHandler.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1

### DrawPointHandler.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 28
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 28

### DrawPolygonHandler.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 54
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 54

### DrawingEvent.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1

### EditPathHandler.as

Violation | Line
--- | ---
A high number of imports can indicate a high degree of coupling within an object. (15 maximum but 17 actually). A high number of imports can indicate a high degree of coupling within an object. Rule counts the number of unique imports and reports a violation if the count is above the user defined threshold. | -1
A high number of imports can indicate a high degree of coupling within an object. (15 maximum but 17 actually). A high number of imports can indicate a high degree of coupling within an object. Rule counts the number of unique imports and reports a violation if the count is above the user defined threshold. | -1
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
Imports from the same package are not necessary. | 20
Imports from the same package are not necessary. | 20
Long parameter list detected (4 maximum, but 6 actually). Long parameter lists can indicate that a new object should be created to wrap the numerous parameters. Basically, try to group the parameters together. | 28
Long parameter list detected (4 maximum, but 6 actually). Long parameter lists can indicate that a new object should be created to wrap the numerous parameters. Basically, try to group the parameters together. | 28
This method is too complex. Maximum complexity is 10, but its cyclomatic complexity was 13 | 73
This method is too complex. Maximum complexity is 10, but its cyclomatic complexity was 13 | 73
This function is far too long (20 maximum, but 32 actually). Violations of this rule usually indicate that the method has too much responsibility. Try to reduce the method size by creating helper methods and removing any copy/pasted code. | 73
This function is far too long (20 maximum, but 32 actually). Violations of this rule usually indicate that the method has too much responsibility. Try to reduce the method size by creating helper methods and removing any copy/pasted code. | 73
This variable (vectorfeatureparent) is not used. | 76
This variable (vectorfeatureparent) is not used. | 76
Using digits at the end of a symbol does not help understanging the meaning of it | 86
Using digits at the end of a symbol does not help understanging the meaning of it | 86
Using digits at the end of a symbol does not help understanging the meaning of it | 87
Using digits at the end of a symbol does not help understanging the meaning of it | 87
Nested if statements are not a good design | 92
Nested if statements are not a good design | 92
Nested if statements are not a good design | 92
Nested if statements are not a good design | 92

### EditPointHandler.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
Long parameter list detected (4 maximum, but 6 actually). Long parameter lists can indicate that a new object should be created to wrap the numerous parameters. Basically, try to group the parameters together. | 31
Long parameter list detected (4 maximum, but 6 actually). Long parameter lists can indicate that a new object should be created to wrap the numerous parameters. Basically, try to group the parameters together. | 31
Too long line (200 maximum, but 200 actually). | 31
Too long line (200 maximum, but 200 actually). | 31
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 59
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 59

### EditPolygonHandler.as

Violation | Line
--- | ---
A high number of imports can indicate a high degree of coupling within an object. (15 maximum but 17 actually). A high number of imports can indicate a high degree of coupling within an object. Rule counts the number of unique imports and reports a violation if the count is above the user defined threshold. | -1
A high number of imports can indicate a high degree of coupling within an object. (15 maximum but 17 actually). A high number of imports can indicate a high degree of coupling within an object. Rule counts the number of unique imports and reports a violation if the count is above the user defined threshold. | -1
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
Imports from the same package are not necessary. | 20
Imports from the same package are not necessary. | 20
Long parameter list detected (4 maximum, but 6 actually). Long parameter lists can indicate that a new object should be created to wrap the numerous parameters. Basically, try to group the parameters together. | 28
Long parameter list detected (4 maximum, but 6 actually). Long parameter lists can indicate that a new object should be created to wrap the numerous parameters. Basically, try to group the parameters together. | 28
Too long line (200 maximum, but 202 actually). | 28
Too long line (200 maximum, but 202 actually). | 28
This method is too complex. Maximum complexity is 10, but its cyclomatic complexity was 12 | 71
This method is too complex. Maximum complexity is 10, but its cyclomatic complexity was 12 | 71
This function is far too long (20 maximum, but 32 actually). Violations of this rule usually indicate that the method has too much responsibility. Try to reduce the method size by creating helper methods and removing any copy/pasted code. | 71
This function is far too long (20 maximum, but 32 actually). Violations of this rule usually indicate that the method has too much responsibility. Try to reduce the method size by creating helper methods and removing any copy/pasted code. | 71
Using digits at the end of a symbol does not help understanging the meaning of it | 84
Using digits at the end of a symbol does not help understanging the meaning of it | 84
Using digits at the end of a symbol does not help understanging the meaning of it | 85
Using digits at the end of a symbol does not help understanging the meaning of it | 85
Nested if statements are not a good design | 90
Nested if statements are not a good design | 90
Nested if statements are not a good design | 90
Nested if statements are not a good design | 90
Nested if statements are not a good design | 111
Nested if statements are not a good design | 111
Nested if statements are not a good design | 111
Nested if statements are not a good design | 111
Nested if statements are not a good design | 112
Nested if statements are not a good design | 112
Nested if statements are not a good design | 119
Nested if statements are not a good design | 119
Nested if statements are not a good design | 119
Nested if statements are not a good design | 119

### ElseFilter.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
This parameter (feature) of this function is not used. | 9
This parameter (feature) of this function is not used. | 9

### Feature.as

Violation | Line
--- | ---
A high number of imports can indicate a high degree of coupling within an object. (15 maximum but 17 actually). A high number of imports can indicate a high degree of coupling within an object. Rule counts the number of unique imports and reports a violation if the count is above the user defined threshold. | -1
A high number of imports can indicate a high degree of coupling within an object. (15 maximum but 17 actually). A high number of imports can indicate a high degree of coupling within an object. Rule counts the number of unique imports and reports a violation if the count is above the user defined threshold. | -1
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
Too many methods detected (10 maximum, but 22 actually). A class with too many methods is probably a good suspect for refactoring, in order to reduce its complexity and find a way to have more fine grained objects. | 27
Too many methods detected (10 maximum, but 22 actually). A class with too many methods is probably a good suspect for refactoring, in order to reduce its complexity and find a way to have more fine grained objects. | 27
Too many public fields or functions detected (10 maximum, but 19 actually). A large number of public methods and attributes declared in a class can indicate the class may need to be broken up as increased effort will be required to thoroughly test it. | 27
Too many public fields or functions detected (10 maximum, but 19 actually). A large number of public methods and attributes declared in a class can indicate the class may need to be broken up as increased effort will be required to thoroughly test it. | 27
Too many field detected (5 maximum, but 12 actually). Classes that have too many fields could be redesigned to have fewer fields, possibly through some nested object grouping of some of the information. For example, a class with city/state/zipcode fields could instead have one Address field. | 27
Too many field detected (5 maximum, but 12 actually). Classes that have too many fields could be redesigned to have fewer fields, possibly through some nested object grouping of some of the information. For example, a class with city/state/zipcode fields could instead have one Address field. | 27
ArrayElementType metadata is not specified for this array-type field (_editionFeaturesArray). | 49
ArrayElementType metadata is not specified for this array-type field (_editionFeaturesArray). | 49
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 61
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 61
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 70
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 70
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 91
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 91
Constructor must be as lightweight as possible. No control statement allowed, whereas a cyclomatic complexe of 7 has been detected. The Just-In-Time compiler does not compile constructors. Make them as lightweight as possible, or move the complexity of the code to a method called by the constructor. Then the complexity will be compiled by the JIT. | 91
Constructor must be as lightweight as possible. No control statement allowed, whereas a cyclomatic complexe of 7 has been detected. The Just-In-Time compiler does not compile constructors. Make them as lightweight as possible, or move the complexity of the code to a method called by the constructor. Then the complexity will be compiled by the JIT. | 91
Long parameter list detected (4 maximum, but 5 actually). Long parameter lists can indicate that a new object should be created to wrap the numerous parameters. Basically, try to group the parameters together. | 91
Long parameter list detected (4 maximum, but 5 actually). Long parameter lists can indicate that a new object should be created to wrap the numerous parameters. Basically, try to group the parameters together. | 91
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 164
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 164
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 168
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 168
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 172
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 172
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 176
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 176
This method is too complex. Maximum complexity is 10, but its cyclomatic complexity was 16 | 342
This method is too complex. Maximum complexity is 10, but its cyclomatic complexity was 16 | 342
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 396
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 396
This parameter (symbolizer) of this function is not used. | 407
This parameter (symbolizer) of this function is not used. | 407
This parameter (symbolizer) of this function is not used. | 411
This parameter (symbolizer) of this function is not used. | 411
Instanciating a variable in a loop can be expensive. | 440
Instanciating a variable in a loop can be expensive. | 440
Instanciating a variable in a loop can be expensive. | 440
Instanciating a variable in a loop can be expensive. | 440
Instanciating a variable in a loop can be expensive. | 440
Instanciating a variable in a loop can be expensive. | 440

### FeatureClickHandler.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
Too many methods detected (10 maximum, but 13 actually). A class with too many methods is probably a good suspect for refactoring, in order to reduce its complexity and find a way to have more fine grained objects. | 20
Too many methods detected (10 maximum, but 13 actually). A class with too many methods is probably a good suspect for refactoring, in order to reduce its complexity and find a way to have more fine grained objects. | 20
Too many field detected (5 maximum, but 12 actually). Classes that have too many fields could be redesigned to have fewer fields, possibly through some nested object grouping of some of the information. For example, a class with city/state/zipcode fields could instead have one Address field. | 20
Too many field detected (5 maximum, but 12 actually). Classes that have too many fields could be redesigned to have fewer fields, possibly through some nested object grouping of some of the information. For example, a class with city/state/zipcode fields could instead have one Address field. | 20
ArrayElementType metadata is not specified for this array-type field (_featureArray). | 26
ArrayElementType metadata is not specified for this array-type field (_featureArray). | 26
Nested if statements are not a good design | 91
Nested if statements are not a good design | 91
This variable (tmppx) seems to be incorrectly named. Let your creativity flow | 131
This variable (tmppx) seems to be incorrectly named. Let your creativity flow | 131
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 143
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 143
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 144
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 144
Nested if statements are not a good design | 145
Nested if statements are not a good design | 145
This variable (vectorfeature) is not used. | 216
This variable (vectorfeature) is not used. | 216

### FeatureEvent.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
ArrayElementType metadata is not specified for this array-type field (_features). | 16
ArrayElementType metadata is not specified for this array-type field (_features). | 16
This parameter (bounds) of this function is not used. | 122
This parameter (bounds) of this function is not used. | 122
Long parameter list detected (4 maximum, but 6 actually). Long parameter lists can indicate that a new object should be created to wrap the numerous parameters. Basically, try to group the parameters together. | 122
Long parameter list detected (4 maximum, but 6 actually). Long parameter lists can indicate that a new object should be created to wrap the numerous parameters. Basically, try to group the parameters together. | 122

### FeatureLayer.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
Too many field detected (5 maximum, but 6 actually). Classes that have too many fields could be redesigned to have fewer fields, possibly through some nested object grouping of some of the information. For example, a class with city/state/zipcode fields could instead have one Address field. | 19
Too many field detected (5 maximum, but 6 actually). Classes that have too many fields could be redesigned to have fewer fields, possibly through some nested object grouping of some of the information. For example, a class with city/state/zipcode fields could instead have one Address field. | 19
ArrayElementType metadata is not specified for this array-type field (_selectedFeatures). | 33
ArrayElementType metadata is not specified for this array-type field (_selectedFeatures). | 33
Long parameter list detected (4 maximum, but 5 actually). Long parameter lists can indicate that a new object should be created to wrap the numerous parameters. Basically, try to group the parameters together. | 37
Long parameter list detected (4 maximum, but 5 actually). Long parameter lists can indicate that a new object should be created to wrap the numerous parameters. Basically, try to group the parameters together. | 37
Flex specific - You must add child only inside the createChildren method | 150
Flex specific - You must add child only inside the createChildren method | 150

### FeatureLayerEditionHandler.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
Too many methods detected (10 maximum, but 11 actually). A class with too many methods is probably a good suspect for refactoring, in order to reduce its complexity and find a way to have more fine grained objects. | 23
Too many methods detected (10 maximum, but 11 actually). A class with too many methods is probably a good suspect for refactoring, in order to reduce its complexity and find a way to have more fine grained objects. | 23
Too many field detected (5 maximum, but 9 actually). Classes that have too many fields could be redesigned to have fewer fields, possibly through some nested object grouping of some of the information. For example, a class with city/state/zipcode fields could instead have one Address field. | 23
Too many field detected (5 maximum, but 9 actually). Classes that have too many fields could be redesigned to have fewer fields, possibly through some nested object grouping of some of the information. For example, a class with city/state/zipcode fields could instead have one Address field. | 23
Long parameter list detected (4 maximum, but 6 actually). Long parameter lists can indicate that a new object should be created to wrap the numerous parameters. Basically, try to group the parameters together. | 49
Long parameter list detected (4 maximum, but 6 actually). Long parameter lists can indicate that a new object should be created to wrap the numerous parameters. Basically, try to group the parameters together. | 49
Nested if statements are not a good design | 80
Nested if statements are not a good design | 80
Nested if statements are not a good design | 99
Nested if statements are not a good design | 99
Nested if statements are not a good design | 115
Nested if statements are not a good design | 115
Nested if statements are not a good design | 132
Nested if statements are not a good design | 132
Nested if statements are not a good design | 156
Nested if statements are not a good design | 156
Nested if statements are not a good design | 163
Nested if statements are not a good design | 163
Nested if statements are not a good design | 187
Nested if statements are not a good design | 187
Nested if statements are not a good design | 232
Nested if statements are not a good design | 232
Flex specific - You must add child only inside the createChildren method | 284
Flex specific - You must add child only inside the createChildren method | 284
This method is too complex. Maximum complexity is 10, but its cyclomatic complexity was 12 | 291
This method is too complex. Maximum complexity is 10, but its cyclomatic complexity was 12 | 291

### Fill.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
This parameter (graphics) of this function is not used. | 14
This parameter (graphics) of this function is not used. | 14

### Format.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 20
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 20
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 20
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 20
This parameter (data) of this function is not used. | 20
This parameter (data) of this function is not used. | 20
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 25
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 25
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 25
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 25
This parameter (features) of this function is not used. | 25
This parameter (features) of this function is not used. | 25

### GMLFormat.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 121
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 121
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 288
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 288
Too long line (200 maximum, but 206 actually). | 306
Too long line (200 maximum, but 206 actually). | 306
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 430
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 430

### Geometry.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
Too many methods detected (10 maximum, but 15 actually). A class with too many methods is probably a good suspect for refactoring, in order to reduce its complexity and find a way to have more fine grained objects. | 13
Too many methods detected (10 maximum, but 15 actually). A class with too many methods is probably a good suspect for refactoring, in order to reduce its complexity and find a way to have more fine grained objects. | 13
Too many public fields or functions detected (10 maximum, but 15 actually). A large number of public methods and attributes declared in a class can indicate the class may need to be broken up as increased effort will be required to thoroughly test it. | 13
Too many public fields or functions detected (10 maximum, but 15 actually). A large number of public methods and attributes declared in a class can indicate the class may need to be broken up as increased effort will be required to thoroughly test it. | 13
This parameter (source) of this function is not used. | 63
This parameter (source) of this function is not used. | 63
This parameter (dest) of this function is not used. | 63
This parameter (dest) of this function is not used. | 63
This parameter (geom) of this function is not used. | 160
This parameter (geom) of this function is not used. | 160
This parameter (geom) of this function is not used. | 172
This parameter (geom) of this function is not used. | 172
This parameter (p) of this function is not used. | 210
This parameter (p) of this function is not used. | 210
Using digits at the end of a symbol does not help understanging the meaning of it | 222
Using digits at the end of a symbol does not help understanging the meaning of it | 222
Using digits at the end of a symbol does not help understanging the meaning of it | 222
Using digits at the end of a symbol does not help understanging the meaning of it | 222
Using digits at the end of a symbol does not help understanging the meaning of it | 238
Using digits at the end of a symbol does not help understanging the meaning of it | 238
Using digits at the end of a symbol does not help understanging the meaning of it | 238
Using digits at the end of a symbol does not help understanging the meaning of it | 238
Using digits at the end of a symbol does not help understanging the meaning of it | 252
Using digits at the end of a symbol does not help understanging the meaning of it | 252
Using digits at the end of a symbol does not help understanging the meaning of it | 253
Using digits at the end of a symbol does not help understanging the meaning of it | 253
Using digits at the end of a symbol does not help understanging the meaning of it | 255
Using digits at the end of a symbol does not help understanging the meaning of it | 255
Using digits at the end of a symbol does not help understanging the meaning of it | 256
Using digits at the end of a symbol does not help understanging the meaning of it | 256
Using digits at the end of a symbol does not help understanging the meaning of it | 258
Using digits at the end of a symbol does not help understanging the meaning of it | 258
Using digits at the end of a symbol does not help understanging the meaning of it | 259
Using digits at the end of a symbol does not help understanging the meaning of it | 259
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 262
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 262
Using digits at the end of a symbol does not help understanging the meaning of it | 264
Using digits at the end of a symbol does not help understanging the meaning of it | 264
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 264
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 264
Using digits at the end of a symbol does not help understanging the meaning of it | 266
Using digits at the end of a symbol does not help understanging the meaning of it | 266
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 266
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 266
This variable (intersection) is not used. | 276
This variable (intersection) is not used. | 276
Using digits at the end of a symbol does not help understanging the meaning of it | 284
Using digits at the end of a symbol does not help understanging the meaning of it | 284
Using digits at the end of a symbol does not help understanging the meaning of it | 285
Using digits at the end of a symbol does not help understanging the meaning of it | 285

### GetCapabilities.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
Too many field detected (5 maximum, but 11 actually). Classes that have too many fields could be redesigned to have fewer fields, possibly through some nested object grouping of some of the information. For example, a class with city/state/zipcode fields could instead have one Address field. | 15
Too many field detected (5 maximum, but 11 actually). Classes that have too many fields could be redesigned to have fewer fields, possibly through some nested object grouping of some of the information. For example, a class with city/state/zipcode fields could instead have one Address field. | 15
ArrayElementType metadata is not specified for this array-type field (VERSIONS). | 17
ArrayElementType metadata is not specified for this array-type field (VERSIONS). | 17
ArrayElementType metadata is not specified for this array-type field (PARSERS). | 18
ArrayElementType metadata is not specified for this array-type field (PARSERS). | 18
ArrayElementType metadata is not specified for this array-type field (versionsToUse). | 20
ArrayElementType metadata is not specified for this array-type field (versionsToUse). | 20
ArrayElementType metadata is not specified for this array-type field (parsersToUse). | 21
ArrayElementType metadata is not specified for this array-type field (parsersToUse). | 21
Long parameter list detected (4 maximum, but 5 actually). Long parameter lists can indicate that a new object should be created to wrap the numerous parameters. Basically, try to group the parameters together. | 40
Long parameter list detected (4 maximum, but 5 actually). Long parameter lists can indicate that a new object should be created to wrap the numerous parameters. Basically, try to group the parameters together. | 40
This method is too complex. Maximum complexity is 10, but its cyclomatic complexity was 12 | 66
This method is too complex. Maximum complexity is 10, but its cyclomatic complexity was 12 | 66
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 80
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 80

### GetFeatureInfoEvent.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 12
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 12
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 19
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 19
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 24
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 24
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 28
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 28

### Grid.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 241
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 241
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 242
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 242
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 314
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 314
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 317
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 317
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 320
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 320

### HTTPRequest.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
ArrayElementType metadata is not specified for this array-type field (_altUrls). | 18
ArrayElementType metadata is not specified for this array-type field (_altUrls). | 18
Long parameter list detected (4 maximum, but 8 actually). Long parameter lists can indicate that a new object should be created to wrap the numerous parameters. Basically, try to group the parameters together. | 22
Long parameter list detected (4 maximum, but 8 actually). Long parameter lists can indicate that a new object should be created to wrap the numerous parameters. Basically, try to group the parameters together. | 22
This parameter (onLoadComplete) of this function is not used. | 23
This parameter (onLoadComplete) of this function is not used. | 23
This method is empty. This should be removed (destroy). This function is not needed. | 31
This method is empty. This should be removed (destroy). This function is not needed. | 31

### Handler.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1

### HashMap.as

Violation | Line
--- | ---
Too many methods detected (10 maximum, but 17 actually). A class with too many methods is probably a good suspect for refactoring, in order to reduce its complexity and find a way to have more fine grained objects. | 71
Too many methods detected (10 maximum, but 17 actually). A class with too many methods is probably a good suspect for refactoring, in order to reduce its complexity and find a way to have more fine grained objects. | 71
Too many public fields or functions detected (10 maximum, but 17 actually). A large number of public methods and attributes declared in a class can indicate the class may need to be broken up as increased effort will be required to thoroughly test it. | 71
Too many public fields or functions detected (10 maximum, but 17 actually). A large number of public methods and attributes declared in a class can indicate the class may need to be broken up as increased effort will be required to thoroughly test it. | 71
Use strongly typed objects instead of *. | 131
Use strongly typed objects instead of *. | 131
Use strongly typed objects instead of *. | 131
Use strongly typed objects instead of *. | 131
Use strongly typed objects instead of *. | 201
Use strongly typed objects instead of *. | 201
Use strongly typed objects instead of *. | 227
Use strongly typed objects instead of *. | 227
Use strongly typed objects instead of *. | 260
Use strongly typed objects instead of *. | 260
Use strongly typed objects instead of *. | 264
Use strongly typed objects instead of *. | 264
Use strongly typed objects instead of *. | 303
Use strongly typed objects instead of *. | 303
Use strongly typed objects instead of *. | 303
Use strongly typed objects instead of *. | 303
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 305
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 305
Use strongly typed objects instead of *. | 307
Use strongly typed objects instead of *. | 307
Use strongly typed objects instead of *. | 344
Use strongly typed objects instead of *. | 344
Use strongly typed objects instead of *. | 373
Use strongly typed objects instead of *. | 373
Use strongly typed objects instead of *. | 373
Use strongly typed objects instead of *. | 373
Use strongly typed objects instead of *. | 403
Use strongly typed objects instead of *. | 403
Use strongly typed objects instead of *. | 435
Use strongly typed objects instead of *. | 435
Use strongly typed objects instead of *. | 490
Use strongly typed objects instead of *. | 490
Use strongly typed objects instead of *. | 521
Use strongly typed objects instead of *. | 521
Use strongly typed objects instead of *. | 523
Use strongly typed objects instead of *. | 523
Use strongly typed objects instead of *. | 555
Use strongly typed objects instead of *. | 555
Use strongly typed objects instead of *. | 586
Use strongly typed objects instead of *. | 586
Use strongly typed objects instead of *. | 588
Use strongly typed objects instead of *. | 588
Use strongly typed objects instead of *. | 609
Use strongly typed objects instead of *. | 609

### HashMapEntry.as

Violation | Line
--- | ---
Use strongly typed objects instead of *. | 44
Use strongly typed objects instead of *. | 44
Use strongly typed objects instead of *. | 52
Use strongly typed objects instead of *. | 52
Use strongly typed objects instead of *. | 64
Use strongly typed objects instead of *. | 64
Use strongly typed objects instead of *. | 64
Use strongly typed objects instead of *. | 64
Use strongly typed objects instead of *. | 78
Use strongly typed objects instead of *. | 78
Use strongly typed objects instead of *. | 91
Use strongly typed objects instead of *. | 91
Use strongly typed objects instead of *. | 104
Use strongly typed objects instead of *. | 104
Use strongly typed objects instead of *. | 117
Use strongly typed objects instead of *. | 117

### IConfiguration.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1

### IControl.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1

### IEditFeature.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1

### IFillSymbolizer.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1

### IFilter.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1

### IGNGeoRMSecurity.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
Too many field detected (5 maximum, but 8 actually). Classes that have too many fields could be redesigned to have fewer fields, possibly through some nested object grouping of some of the information. For example, a class with city/state/zipcode fields could instead have one Address field. | 20
Too many field detected (5 maximum, but 8 actually). Classes that have too many fields could be redesigned to have fewer fields, possibly through some nested object grouping of some of the information. For example, a class with city/state/zipcode fields could instead have one Address field. | 20
Constructor must be as lightweight as possible. No control statement allowed, whereas a cyclomatic complexe of 3 has been detected. The Just-In-Time compiler does not compile constructors. Make them as lightweight as possible, or move the complexity of the code to a method called by the constructor. Then the complexity will be compiled by the JIT. | 61
Constructor must be as lightweight as possible. No control statement allowed, whereas a cyclomatic complexe of 3 has been detected. The Just-In-Time compiler does not compile constructors. Make them as lightweight as possible, or move the complexity of the code to a method called by the constructor. Then the complexity will be compiled by the JIT. | 61
This private method (configResponse) does not seem to be used. | 124
This private method (configResponse) does not seem to be used. | 124
This private method (configUrl) does not seem to be used. | 140
This private method (configUrl) does not seem to be used. | 140

### IHandler.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1

### IHashMapEntry.as

Violation | Line
--- | ---
Use strongly typed objects instead of *. | 55
Use strongly typed objects instead of *. | 55
Use strongly typed objects instead of *. | 65
Use strongly typed objects instead of *. | 65
Use strongly typed objects instead of *. | 75
Use strongly typed objects instead of *. | 75
Use strongly typed objects instead of *. | 85
Use strongly typed objects instead of *. | 85

### IHttpParams.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1

### IMap.as

Violation | Line
--- | ---
Too many methods detected (10 maximum, but 17 actually). A class with too many methods is probably a good suspect for refactoring, in order to reduce its complexity and find a way to have more fine grained objects. | 37
Too many methods detected (10 maximum, but 17 actually). A class with too many methods is probably a good suspect for refactoring, in order to reduce its complexity and find a way to have more fine grained objects. | 37
Use strongly typed objects instead of *. | 47
Use strongly typed objects instead of *. | 47
Use strongly typed objects instead of *. | 47
Use strongly typed objects instead of *. | 47
Use strongly typed objects instead of *. | 78
Use strongly typed objects instead of *. | 78
Use strongly typed objects instead of *. | 88
Use strongly typed objects instead of *. | 88
Use strongly typed objects instead of *. | 98
Use strongly typed objects instead of *. | 98
Use strongly typed objects instead of *. | 108
Use strongly typed objects instead of *. | 108
Use strongly typed objects instead of *. | 108
Use strongly typed objects instead of *. | 108
Use strongly typed objects instead of *. | 118
Use strongly typed objects instead of *. | 118
Use strongly typed objects instead of *. | 118
Use strongly typed objects instead of *. | 118
Use strongly typed objects instead of *. | 168
Use strongly typed objects instead of *. | 168
Use strongly typed objects instead of *. | 183
Use strongly typed objects instead of *. | 183

### IRequest.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1

### ISecurity.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1

### IStrokeSymbolizer.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1

### ImageLayer.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
Long parameter list detected (4 maximum, but 7 actually). Long parameter lists can indicate that a new object should be created to wrap the numerous parameters. Basically, try to group the parameters together. | 25
Long parameter list detected (4 maximum, but 7 actually). Long parameter lists can indicate that a new object should be created to wrap the numerous parameters. Basically, try to group the parameters together. | 25
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 70
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 70
Flex specific - You must add child only inside the createChildren method | 84
Flex specific - You must add child only inside the createChildren method | 84

### ImageTile.as

Violation | Line
--- | ---
A high number of imports can indicate a high degree of coupling within an object. (15 maximum but 16 actually). A high number of imports can indicate a high degree of coupling within an object. Rule counts the number of unique imports and reports a violation if the count is above the user defined threshold. | -1
A high number of imports can indicate a high degree of coupling within an object. (15 maximum but 16 actually). A high number of imports can indicate a high degree of coupling within an object. Rule counts the number of unique imports and reports a violation if the count is above the user defined threshold. | -1
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
Long parameter list detected (4 maximum, but 5 actually). Long parameter lists can indicate that a new object should be created to wrap the numerous parameters. Basically, try to group the parameters together. | 34
Long parameter list detected (4 maximum, but 5 actually). Long parameter lists can indicate that a new object should be created to wrap the numerous parameters. Basically, try to group the parameters together. | 34
Flex specific - You must add child only inside the createChildren method | 115
Flex specific - You must add child only inside the createChildren method | 115
Flex specific - You must add child only inside the createChildren method | 119
Flex specific - You must add child only inside the createChildren method | 119

### IntersectsFilter.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1

### KML.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
Long parameter list detected (4 maximum, but 7 actually). Long parameter lists can indicate that a new object should be created to wrap the numerous parameters. Basically, try to group the parameters together. | 21
Long parameter list detected (4 maximum, but 7 actually). Long parameter lists can indicate that a new object should be created to wrap the numerous parameters. Basically, try to group the parameters together. | 21

### KMLFormat.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1

### Layer.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
Too many methods detected (10 maximum, but 15 actually). A class with too many methods is probably a good suspect for refactoring, in order to reduce its complexity and find a way to have more fine grained objects. | 23
Too many methods detected (10 maximum, but 15 actually). A class with too many methods is probably a good suspect for refactoring, in order to reduce its complexity and find a way to have more fine grained objects. | 23
Too many public fields or functions detected (10 maximum, but 14 actually). A large number of public methods and attributes declared in a class can indicate the class may need to be broken up as increased effort will be required to thoroughly test it. | 23
Too many public fields or functions detected (10 maximum, but 14 actually). A large number of public methods and attributes declared in a class can indicate the class may need to be broken up as increased effort will be required to thoroughly test it. | 23
Too many field detected (5 maximum, but 13 actually). Classes that have too many fields could be redesigned to have fewer fields, possibly through some nested object grouping of some of the information. For example, a class with city/state/zipcode fields could instead have one Address field. | 23
Too many field detected (5 maximum, but 13 actually). Classes that have too many fields could be redesigned to have fewer fields, possibly through some nested object grouping of some of the information. For example, a class with city/state/zipcode fields could instead have one Address field. | 23
ArrayElementType metadata is not specified for this array-type field (_resolutions). | 41
ArrayElementType metadata is not specified for this array-type field (_resolutions). | 41
Constructor must be as lightweight as possible. No control statement allowed, whereas a cyclomatic complexe of 3 has been detected. The Just-In-Time compiler does not compile constructors. Make them as lightweight as possible, or move the complexity of the code to a method called by the constructor. Then the complexity will be compiled by the JIT. | 55
Constructor must be as lightweight as possible. No control statement allowed, whereas a cyclomatic complexe of 3 has been detected. The Just-In-Time compiler does not compile constructors. Make them as lightweight as possible, or move the complexity of the code to a method called by the constructor. Then the complexity will be compiled by the JIT. | 55
Long parameter list detected (4 maximum, but 6 actually). Long parameter lists can indicate that a new object should be created to wrap the numerous parameters. Basically, try to group the parameters together. | 55
Long parameter list detected (4 maximum, but 6 actually). Long parameter lists can indicate that a new object should be created to wrap the numerous parameters. Basically, try to group the parameters together. | 55
This parameter (setNewBaseLayer) of this function is not used. | 102
This parameter (setNewBaseLayer) of this function is not used. | 102
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 214
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 214
This parameter (fullRedraw) of this function is not used. | 254
This parameter (fullRedraw) of this function is not used. | 254
This test contains a hard coded boolean value. You could remove it by having 'condition' | 266
This test contains a hard coded boolean value. You could remove it by having 'condition' | 266
This parameter (bounds) of this function is not used. | 277
This parameter (bounds) of this function is not used. | 277
This test contains a hard coded boolean value. You could remove it by having 'condition' | 514
This test contains a hard coded boolean value. You could remove it by having 'condition' | 514
This test contains a hard coded boolean value. You could remove it by having 'condition' | 519
This test contains a hard coded boolean value. You could remove it by having 'condition' | 519

### LayerEvent.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1

### LayerSwitcher.as

Violation | Line
--- | ---
A high number of imports can indicate a high degree of coupling within an object. (15 maximum but 16 actually). A high number of imports can indicate a high degree of coupling within an object. Rule counts the number of unique imports and reports a violation if the count is above the user defined threshold. | -1
A high number of imports can indicate a high degree of coupling within an object. (15 maximum but 16 actually). A high number of imports can indicate a high degree of coupling within an object. Rule counts the number of unique imports and reports a violation if the count is above the user defined threshold. | -1
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
Too many methods detected (10 maximum, but 13 actually). A class with too many methods is probably a good suspect for refactoring, in order to reduce its complexity and find a way to have more fine grained objects. | 26
Too many methods detected (10 maximum, but 13 actually). A class with too many methods is probably a good suspect for refactoring, in order to reduce its complexity and find a way to have more fine grained objects. | 26
Too many field detected (5 maximum, but 14 actually). Classes that have too many fields could be redesigned to have fewer fields, possibly through some nested object grouping of some of the information. For example, a class with city/state/zipcode fields could instead have one Address field. | 26
Too many field detected (5 maximum, but 14 actually). Classes that have too many fields could be redesigned to have fewer fields, possibly through some nested object grouping of some of the information. For example, a class with city/state/zipcode fields could instead have one Address field. | 26
This private attribute (_oldMouseX) does not seem to be used. | 39
This private attribute (_oldMouseX) does not seem to be used. | 39
Embed metadata detected in source code where a stylesheet may be cleaner | 52
Embed metadata detected in source code where a stylesheet may be cleaner | 52
Embed metadata detected in source code where a stylesheet may be cleaner | 55
Embed metadata detected in source code where a stylesheet may be cleaner | 55
This method is too complex. Maximum complexity is 10, but its cyclomatic complexity was 22 | 121
This method is too complex. Maximum complexity is 10, but its cyclomatic complexity was 22 | 121
This function is far too long (20 maximum, but 131 actually). Violations of this rule usually indicate that the method has too much responsibility. Try to reduce the method size by creating helper methods and removing any copy/pasted code. | 121
This function is far too long (20 maximum, but 131 actually). Violations of this rule usually indicate that the method has too much responsibility. Try to reduce the method size by creating helper methods and removing any copy/pasted code. | 121
Flex specific - You must add child only inside the createChildren method | 132
Flex specific - You must add child only inside the createChildren method | 132
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 163
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 163
Flex specific - You must add child only inside the createChildren method | 169
Flex specific - You must add child only inside the createChildren method | 169
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 172
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 172
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 173
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 173
Nested if statements are not a good design | 182
Nested if statements are not a good design | 182
Nested if statements are not a good design | 182
Nested if statements are not a good design | 182
Instanciating a variable in a loop can be expensive. | 185
Instanciating a variable in a loop can be expensive. | 185
Instanciating a variable in a loop can be expensive. | 185
Instanciating a variable in a loop can be expensive. | 185
Instanciating a variable in a loop can be expensive. | 185
Instanciating a variable in a loop can be expensive. | 185
Instanciating a variable in a loop can be expensive. | 190
Instanciating a variable in a loop can be expensive. | 190
Instanciating a variable in a loop can be expensive. | 190
Instanciating a variable in a loop can be expensive. | 190
Instanciating a variable in a loop can be expensive. | 190
Instanciating a variable in a loop can be expensive. | 190
Instanciating a variable in a loop can be expensive. | 198
Instanciating a variable in a loop can be expensive. | 198
Instanciating a variable in a loop can be expensive. | 198
Instanciating a variable in a loop can be expensive. | 198
Instanciating a variable in a loop can be expensive. | 206
Instanciating a variable in a loop can be expensive. | 206
Instanciating a variable in a loop can be expensive. | 206
Instanciating a variable in a loop can be expensive. | 206
Instanciating a variable in a loop can be expensive. | 207
Instanciating a variable in a loop can be expensive. | 207
Instanciating a variable in a loop can be expensive. | 207
Instanciating a variable in a loop can be expensive. | 207
Nested if statements are not a good design | 209
Nested if statements are not a good design | 209
Nested if statements are not a good design | 209
Nested if statements are not a good design | 209
Instanciating a variable in a loop can be expensive. | 228
Instanciating a variable in a loop can be expensive. | 228
Instanciating a variable in a loop can be expensive. | 228
Instanciating a variable in a loop can be expensive. | 228
Flex specific - You must add child only inside the createChildren method | 236
Flex specific - You must add child only inside the createChildren method | 236
Flex specific - You must add child only inside the createChildren method | 237
Flex specific - You must add child only inside the createChildren method | 237
Flex specific - You must add child only inside the createChildren method | 238
Flex specific - You must add child only inside the createChildren method | 238
Flex specific - You must add child only inside the createChildren method | 239
Flex specific - You must add child only inside the createChildren method | 239
Flex specific - You must add child only inside the createChildren method | 240
Flex specific - You must add child only inside the createChildren method | 240
Flex specific - You must add child only inside the createChildren method | 264
Flex specific - You must add child only inside the createChildren method | 264
Nested if statements are not a good design | 271
Nested if statements are not a good design | 271
Nested if statements are not a good design | 271
Nested if statements are not a good design | 271
Instanciating a variable in a loop can be expensive. | 280
Instanciating a variable in a loop can be expensive. | 280
Instanciating a variable in a loop can be expensive. | 280
Instanciating a variable in a loop can be expensive. | 280
Instanciating a variable in a loop can be expensive. | 288
Instanciating a variable in a loop can be expensive. | 288
Instanciating a variable in a loop can be expensive. | 288
Instanciating a variable in a loop can be expensive. | 288
Instanciating a variable in a loop can be expensive. | 296
Instanciating a variable in a loop can be expensive. | 296
Instanciating a variable in a loop can be expensive. | 296
Instanciating a variable in a loop can be expensive. | 296
Instanciating a variable in a loop can be expensive. | 297
Instanciating a variable in a loop can be expensive. | 297
Instanciating a variable in a loop can be expensive. | 297
Instanciating a variable in a loop can be expensive. | 297
Nested if statements are not a good design | 299
Nested if statements are not a good design | 299
Nested if statements are not a good design | 299
Nested if statements are not a good design | 299
Instanciating a variable in a loop can be expensive. | 318
Instanciating a variable in a loop can be expensive. | 318
Instanciating a variable in a loop can be expensive. | 318
Instanciating a variable in a loop can be expensive. | 318
Nested if statements are not a good design | 319
Nested if statements are not a good design | 319
Instanciating a variable in a loop can be expensive. | 327
Instanciating a variable in a loop can be expensive. | 327
Instanciating a variable in a loop can be expensive. | 327
Instanciating a variable in a loop can be expensive. | 327
Instanciating a variable in a loop can be expensive. | 328
Instanciating a variable in a loop can be expensive. | 328
Instanciating a variable in a loop can be expensive. | 328
Instanciating a variable in a loop can be expensive. | 328
Flex specific - You must add child only inside the createChildren method | 335
Flex specific - You must add child only inside the createChildren method | 335
Flex specific - You must add child only inside the createChildren method | 336
Flex specific - You must add child only inside the createChildren method | 336
Flex specific - You must add child only inside the createChildren method | 337
Flex specific - You must add child only inside the createChildren method | 337
Flex specific - You must add child only inside the createChildren method | 338
Flex specific - You must add child only inside the createChildren method | 338
Flex specific - You must add child only inside the createChildren method | 339
Flex specific - You must add child only inside the createChildren method | 339
Flex specific - You must add child only inside the createChildren method | 340
Flex specific - You must add child only inside the createChildren method | 340
Flex specific - You must add child only inside the createChildren method | 341
Flex specific - You must add child only inside the createChildren method | 341
Flex specific - You must add child only inside the createChildren method | 353
Flex specific - You must add child only inside the createChildren method | 353
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 407
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 407
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 441
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 441
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 442
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 442
This variable (tween) is not used. | 445
This variable (tween) is not used. | 445
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 491
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 491
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 492
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 492

### LineString.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
Constructor must be as lightweight as possible. No control statement allowed, whereas a cyclomatic complexe of 8 has been detected. The Just-In-Time compiler does not compile constructors. Make them as lightweight as possible, or move the complexity of the code to a method called by the constructor. Then the complexity will be compiled by the JIT. | 17
Constructor must be as lightweight as possible. No control statement allowed, whereas a cyclomatic complexe of 8 has been detected. The Just-In-Time compiler does not compile constructors. Make them as lightweight as possible, or move the complexity of the code to a method called by the constructor. Then the complexity will be compiled by the JIT. | 17
This method is too complex. Maximum complexity is 10, but its cyclomatic complexity was 11 | 138
This method is too complex. Maximum complexity is 10, but its cyclomatic complexity was 11 | 138
This function is far too long (20 maximum, but 22 actually). Violations of this rule usually indicate that the method has too much responsibility. Try to reduce the method size by creating helper methods and removing any copy/pasted code. | 138
This function is far too long (20 maximum, but 22 actually). Violations of this rule usually indicate that the method has too much responsibility. Try to reduce the method size by creating helper methods and removing any copy/pasted code. | 138
Using digits at the end of a symbol does not help understanging the meaning of it | 158
Using digits at the end of a symbol does not help understanging the meaning of it | 158
Using digits at the end of a symbol does not help understanging the meaning of it | 159
Using digits at the end of a symbol does not help understanging the meaning of it | 159
Using digits at the end of a symbol does not help understanging the meaning of it | 161
Using digits at the end of a symbol does not help understanging the meaning of it | 161
Using digits at the end of a symbol does not help understanging the meaning of it | 162
Using digits at the end of a symbol does not help understanging the meaning of it | 162
Using digits at the end of a symbol does not help understanging the meaning of it | 227
Using digits at the end of a symbol does not help understanging the meaning of it | 227

### LineStringFeature.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 16
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 16
This parameter (editionFeatureParentGeometry) of this function is not used. | 16
This parameter (editionFeatureParentGeometry) of this function is not used. | 16
Long parameter list detected (4 maximum, but 6 actually). Long parameter lists can indicate that a new object should be created to wrap the numerous parameters. Basically, try to group the parameters together. | 16
Long parameter list detected (4 maximum, but 6 actually). Long parameter lists can indicate that a new object should be created to wrap the numerous parameters. Basically, try to group the parameters together. | 16
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 30
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 30
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 31
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 31
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 32
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 32
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 34
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 34
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 35
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 35

### LineSymbolizer.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1

### LinearRing.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 48
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 48
Using digits at the end of a symbol does not help understanging the meaning of it | 49
Using digits at the end of a symbol does not help understanging the meaning of it | 49
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 49
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 49
Using digits at the end of a symbol does not help understanging the meaning of it | 50
Using digits at the end of a symbol does not help understanging the meaning of it | 50
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 50
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 50
Nested if statements are not a good design | 60
Nested if statements are not a good design | 60
Nested if statements are not a good design | 66
Nested if statements are not a good design | 66
Nested if statements are not a good design | 108
Nested if statements are not a good design | 108

### LonLat.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 36
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 36

### Map.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 311
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 311
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 355
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 355
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 401
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 401
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 547
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 547
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 548
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 548
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 550
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 550
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 551
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 551
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 660
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 660
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 673
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 673
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 674
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 674
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 686
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 686
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 687
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 687
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 705
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 705
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 859
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 859
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 860
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 860

### MapEvent.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1

### Maplint.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
Long parameter list detected (4 maximum, but 5 actually). Long parameter lists can indicate that a new object should be created to wrap the numerous parameters. Basically, try to group the parameters together. | 13
Long parameter list detected (4 maximum, but 5 actually). Long parameter lists can indicate that a new object should be created to wrap the numerous parameters. Basically, try to group the parameters together. | 13

### Mapnik.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
Long parameter list detected (4 maximum, but 5 actually). Long parameter lists can indicate that a new object should be created to wrap the numerous parameters. Basically, try to group the parameters together. | 13
Long parameter list detected (4 maximum, but 5 actually). Long parameter lists can indicate that a new object should be created to wrap the numerous parameters. Basically, try to group the parameters together. | 13

### Marker.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 21
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 21
Embed metadata detected in source code where a stylesheet may be cleaner | 42
Embed metadata detected in source code where a stylesheet may be cleaner | 42

### MousePosition.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
Too many field detected (5 maximum, but 8 actually). Classes that have too many fields could be redesigned to have fewer fields, possibly through some nested object grouping of some of the information. For example, a class with city/state/zipcode fields could instead have one Address field. | 17
Too many field detected (5 maximum, but 8 actually). Classes that have too many fields could be redesigned to have fewer fields, possibly through some nested object grouping of some of the information. For example, a class with city/state/zipcode fields could instead have one Address field. | 17
Flex specific - You must add child only inside the createChildren method | 70
Flex specific - You must add child only inside the createChildren method | 70

### MultiLineString.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 37
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 37

### MultiLineStringFeature.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 16
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 16
This parameter (editionFeatureParentGeometry) of this function is not used. | 16
This parameter (editionFeatureParentGeometry) of this function is not used. | 16
Long parameter list detected (4 maximum, but 6 actually). Long parameter lists can indicate that a new object should be created to wrap the numerous parameters. Basically, try to group the parameters together. | 16
Long parameter list detected (4 maximum, but 6 actually). Long parameter lists can indicate that a new object should be created to wrap the numerous parameters. Basically, try to group the parameters together. | 16
Too long line (200 maximum, but 205 actually). | 16
Too long line (200 maximum, but 205 actually). | 16
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 31
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 31
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 32
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 32
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 33
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 33
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 35
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 35
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 36
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 36
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 38
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 38

### MultiPoint.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 32
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 32

### MultiPointFeature.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 16
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 16
This parameter (editionFeatureParentGeometry) of this function is not used. | 16
This parameter (editionFeatureParentGeometry) of this function is not used. | 16
Long parameter list detected (4 maximum, but 6 actually). Long parameter lists can indicate that a new object should be created to wrap the numerous parameters. Basically, try to group the parameters together. | 16
Long parameter list detected (4 maximum, but 6 actually). Long parameter lists can indicate that a new object should be created to wrap the numerous parameters. Basically, try to group the parameters together. | 16
Nested if statements are not a good design | 28
Nested if statements are not a good design | 28
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 41
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 41
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 42
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 42
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 43
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 43
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 45
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 45
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 46
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 46
Long switch case detected (3 lines maximum, but 5 actually). A switch case statement should be either empty, or contain a break, or call another method. | 63
Long switch case detected (3 lines maximum, but 5 actually). A switch case statement should be either empty, or contain a break, or call another method. | 63

### MultiPolygon.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 33
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 33

### MultiPolygonFeature.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 18
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 18
This parameter (editionFeatureParentGeometry) of this function is not used. | 18
This parameter (editionFeatureParentGeometry) of this function is not used. | 18
Long parameter list detected (4 maximum, but 6 actually). Long parameter lists can indicate that a new object should be created to wrap the numerous parameters. Basically, try to group the parameters together. | 18
Long parameter list detected (4 maximum, but 6 actually). Long parameter lists can indicate that a new object should be created to wrap the numerous parameters. Basically, try to group the parameters together. | 18
Too long line (200 maximum, but 200 actually). | 18
Too long line (200 maximum, but 200 actually). | 18
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 30
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 30
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 31
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 31
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 32
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 32
This variable (pAux) is not used. | 33
This variable (pAux) is not used. | 33
This variable (count) is not used. | 34
This variable (count) is not used. | 34
This variable (countFeature) is not used. | 35
This variable (countFeature) is not used. | 35
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 37
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 37
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 38
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 38
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 39
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 39
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 40
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 40

### OGCParams.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1

### OSM.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 34
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 34
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 35
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 35
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 36
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 36

### OpenScalesEvent.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
The clone event must be overiden in a custom event. When creating your own custom Event class, you must override the inherited Event.clone() method in order for it to duplicate the properties of your custom class. If you do not set all the properties that you add in your event subclass, those properties will not have the correct values when the event is cloned. This is important because the Flex SDK clones events whenever redispatching takes place. | 8
The clone event must be overiden in a custom event. When creating your own custom Event class, you must override the inherited Event.clone() method in order for it to duplicate the properties of your custom class. If you do not set all the properties that you add in your event subclass, those properties will not have the correct values when the event is cloned. This is important because the Flex SDK clones events whenever redispatching takes place. | 8

### Osmarender.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
Long parameter list detected (4 maximum, but 5 actually). Long parameter lists can indicate that a new object should be created to wrap the numerous parameters. Basically, try to group the parameters together. | 13
Long parameter list detected (4 maximum, but 5 actually). Long parameter lists can indicate that a new object should be created to wrap the numerous parameters. Basically, try to group the parameters together. | 13

### PanZoom.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
Too many field detected (5 maximum, but 14 actually). Classes that have too many fields could be redesigned to have fewer fields, possibly through some nested object grouping of some of the information. For example, a class with city/state/zipcode fields could instead have one Address field. | 15
Too many field detected (5 maximum, but 14 actually). Classes that have too many fields could be redesigned to have fewer fields, possibly through some nested object grouping of some of the information. For example, a class with city/state/zipcode fields could instead have one Address field. | 15
If this field (X) was meant to be a constant, make it constant. Otherwise, if it is used as a global variable, you may want to redesign this class | 18
If this field (X) was meant to be a constant, make it constant. Otherwise, if it is used as a global variable, you may want to redesign this class | 18
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 18
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 18
If this field (Y) was meant to be a constant, make it constant. Otherwise, if it is used as a global variable, you may want to redesign this class | 19
If this field (Y) was meant to be a constant, make it constant. Otherwise, if it is used as a global variable, you may want to redesign this class | 19
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 19
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 19
ArrayElementType metadata is not specified for this array-type field (_buttons). | 21
ArrayElementType metadata is not specified for this array-type field (_buttons). | 21
Embed metadata detected in source code where a stylesheet may be cleaner | 25
Embed metadata detected in source code where a stylesheet may be cleaner | 25
Embed metadata detected in source code where a stylesheet may be cleaner | 28
Embed metadata detected in source code where a stylesheet may be cleaner | 28
Embed metadata detected in source code where a stylesheet may be cleaner | 31
Embed metadata detected in source code where a stylesheet may be cleaner | 31
Embed metadata detected in source code where a stylesheet may be cleaner | 34
Embed metadata detected in source code where a stylesheet may be cleaner | 34
Embed metadata detected in source code where a stylesheet may be cleaner | 37
Embed metadata detected in source code where a stylesheet may be cleaner | 37
Embed metadata detected in source code where a stylesheet may be cleaner | 40
Embed metadata detected in source code where a stylesheet may be cleaner | 40
Embed metadata detected in source code where a stylesheet may be cleaner | 43
Embed metadata detected in source code where a stylesheet may be cleaner | 43
Embed metadata detected in source code where a stylesheet may be cleaner | 46
Embed metadata detected in source code where a stylesheet may be cleaner | 46
Embed metadata detected in source code where a stylesheet may be cleaner | 49
Embed metadata detected in source code where a stylesheet may be cleaner | 49
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 71
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 71
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 76
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 76
This parameter (alt) of this function is not used. | 100
This parameter (alt) of this function is not used. | 100
Long parameter list detected (4 maximum, but 5 actually). Long parameter lists can indicate that a new object should be created to wrap the numerous parameters. Basically, try to group the parameters together. | 100
Long parameter list detected (4 maximum, but 5 actually). Long parameter lists can indicate that a new object should be created to wrap the numerous parameters. Basically, try to group the parameters together. | 100
Flex specific - You must add child only inside the createChildren method | 104
Flex specific - You must add child only inside the createChildren method | 104

### PanZoomBar.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
Too many field detected (5 maximum, but 7 actually). Classes that have too many fields could be redesigned to have fewer fields, possibly through some nested object grouping of some of the information. For example, a class with city/state/zipcode fields could instead have one Address field. | 19
Too many field detected (5 maximum, but 7 actually). Classes that have too many fields could be redesigned to have fewer fields, possibly through some nested object grouping of some of the information. For example, a class with city/state/zipcode fields could instead have one Address field. | 19
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 69
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 69
This parameter (obt) of this function is not used. | 69
This parameter (obt) of this function is not used. | 69
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 84
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 84
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 85
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 85
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 110
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 110
Flex specific - You must add child only inside the createChildren method | 129
Flex specific - You must add child only inside the createChildren method | 129
Flex specific - You must add child only inside the createChildren method | 132
Flex specific - You must add child only inside the createChildren method | 132
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 148
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 148

### Pixel.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 9
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 9
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 10
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 10

### Point.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 14
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 14
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 16
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 16
Using digits at the end of a symbol does not help understanging the meaning of it | 48
Using digits at the end of a symbol does not help understanging the meaning of it | 48
Using digits at the end of a symbol does not help understanging the meaning of it | 49
Using digits at the end of a symbol does not help understanging the meaning of it | 49
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 90
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 90

### PointFeature.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 72
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 72
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 73
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 73
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 75
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 75
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 76
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 76
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 104
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 104
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 105
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 105
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 107
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 107
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 108
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 108
Too long line (200 maximum, but 254 actually). | 189
Too long line (200 maximum, but 254 actually). | 189

### PointSymbolizer.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1

### Polygon.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
Constructor must be as lightweight as possible. No control statement allowed, whereas a cyclomatic complexe of 8 has been detected. The Just-In-Time compiler does not compile constructors. Make them as lightweight as possible, or move the complexity of the code to a method called by the constructor. Then the complexity will be compiled by the JIT. | 20
Constructor must be as lightweight as possible. No control statement allowed, whereas a cyclomatic complexe of 8 has been detected. The Just-In-Time compiler does not compile constructors. Make them as lightweight as possible, or move the complexity of the code to a method called by the constructor. Then the complexity will be compiled by the JIT. | 20
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 57
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 57
This method is too complex. Maximum complexity is 10, but its cyclomatic complexity was 11 | 149
This method is too complex. Maximum complexity is 10, but its cyclomatic complexity was 11 | 149
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 156
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 156
Nested if statements are not a good design | 186
Nested if statements are not a good design | 186
Nested if statements are not a good design | 186
Nested if statements are not a good design | 186
Nested if statements are not a good design | 196
Nested if statements are not a good design | 196
Instanciating a variable in a loop can be expensive. | 269
Instanciating a variable in a loop can be expensive. | 269

### PolygonFeature.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 16
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 16
This parameter (editionFeatureParentGeometry) of this function is not used. | 16
This parameter (editionFeatureParentGeometry) of this function is not used. | 16
Long parameter list detected (4 maximum, but 6 actually). Long parameter lists can indicate that a new object should be created to wrap the numerous parameters. Basically, try to group the parameters together. | 16
Long parameter list detected (4 maximum, but 6 actually). Long parameter lists can indicate that a new object should be created to wrap the numerous parameters. Basically, try to group the parameters together. | 16
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 27
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 27
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 28
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 28
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 29
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 29
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 31
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 31
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 32
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 32
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 34
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 34

### PolygonSymbolizer.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1

### Popup.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
Too many field detected (5 maximum, but 14 actually). Classes that have too many fields could be redesigned to have fewer fields, possibly through some nested object grouping of some of the information. For example, a class with city/state/zipcode fields could instead have one Address field. | 22
Too many field detected (5 maximum, but 14 actually). Classes that have too many fields could be redesigned to have fewer fields, possibly through some nested object grouping of some of the information. For example, a class with city/state/zipcode fields could instead have one Address field. | 22
If this field (WIDTH) was meant to be a constant, make it constant. Otherwise, if it is used as a global variable, you may want to redesign this class | 25
If this field (WIDTH) was meant to be a constant, make it constant. Otherwise, if it is used as a global variable, you may want to redesign this class | 25
If this field (HEIGHT) was meant to be a constant, make it constant. Otherwise, if it is used as a global variable, you may want to redesign this class | 26
If this field (HEIGHT) was meant to be a constant, make it constant. Otherwise, if it is used as a global variable, you may want to redesign this class | 26
If this field (BACKGROUND) was meant to be a constant, make it constant. Otherwise, if it is used as a global variable, you may want to redesign this class | 27
If this field (BACKGROUND) was meant to be a constant, make it constant. Otherwise, if it is used as a global variable, you may want to redesign this class | 27
If this field (BORDER) was meant to be a constant, make it constant. Otherwise, if it is used as a global variable, you may want to redesign this class | 28
If this field (BORDER) was meant to be a constant, make it constant. Otherwise, if it is used as a global variable, you may want to redesign this class | 28
Embed metadata detected in source code where a stylesheet may be cleaner | 41
Embed metadata detected in source code where a stylesheet may be cleaner | 41
Constructor must be as lightweight as possible. No control statement allowed, whereas a cyclomatic complexe of 4 has been detected. The Just-In-Time compiler does not compile constructors. Make them as lightweight as possible, or move the complexity of the code to a method called by the constructor. Then the complexity will be compiled by the JIT. | 43
Constructor must be as lightweight as possible. No control statement allowed, whereas a cyclomatic complexe of 4 has been detected. The Just-In-Time compiler does not compile constructors. Make them as lightweight as possible, or move the complexity of the code to a method called by the constructor. Then the complexity will be compiled by the JIT. | 43
Long parameter list detected (4 maximum, but 6 actually). Long parameter lists can indicate that a new object should be created to wrap the numerous parameters. Basically, try to group the parameters together. | 43
Long parameter list detected (4 maximum, but 6 actually). Long parameter lists can indicate that a new object should be created to wrap the numerous parameters. Basically, try to group the parameters together. | 43
This test contains a hard coded boolean value. You could remove it by having 'condition' | 114
This test contains a hard coded boolean value. You could remove it by having 'condition' | 114
Flex specific - You must add child only inside the createChildren method | 120
Flex specific - You must add child only inside the createChildren method | 120
Flex specific - You must add child only inside the createChildren method | 136
Flex specific - You must add child only inside the createChildren method | 136

### RadioButton.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
Embed metadata detected in source code where a stylesheet may be cleaner | 15
Embed metadata detected in source code where a stylesheet may be cleaner | 15
Embed metadata detected in source code where a stylesheet may be cleaner | 18
Embed metadata detected in source code where a stylesheet may be cleaner | 18
Constructor must be as lightweight as possible. No control statement allowed, whereas a cyclomatic complexe of 2 has been detected. The Just-In-Time compiler does not compile constructors. Make them as lightweight as possible, or move the complexity of the code to a method called by the constructor. Then the complexity will be compiled by the JIT. | 24
Constructor must be as lightweight as possible. No control statement allowed, whereas a cyclomatic complexe of 2 has been detected. The Just-In-Time compiler does not compile constructors. Make them as lightweight as possible, or move the complexity of the code to a method called by the constructor. Then the complexity will be compiled by the JIT. | 24
This test contains a hard coded boolean value. You could remove it by having '!condition' | 46
This test contains a hard coded boolean value. You could remove it by having '!condition' | 46
Flex specific - You must add child only inside the createChildren method | 51
Flex specific - You must add child only inside the createChildren method | 51

### Rule.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
Too many field detected (5 maximum, but 7 actually). Classes that have too many fields could be redesigned to have fewer fields, possibly through some nested object grouping of some of the information. For example, a class with city/state/zipcode fields could instead have one Address field. | 14
Too many field detected (5 maximum, but 7 actually). Classes that have too many fields could be redesigned to have fewer fields, possibly through some nested object grouping of some of the information. For example, a class with city/state/zipcode fields could instead have one Address field. | 14
ArrayElementType metadata is not specified for this array-type field (_symbolizers). | 34
ArrayElementType metadata is not specified for this array-type field (_symbolizers). | 34
This parameter (symbolizer) of this function is not used. | 229
This parameter (symbolizer) of this function is not used. | 229
Nested if statements are not a good design | 242
Nested if statements are not a good design | 242
Long switch case detected (3 lines maximum, but 6 actually). A switch case statement should be either empty, or contain a break, or call another method. | 265
Long switch case detected (3 lines maximum, but 6 actually). A switch case statement should be either empty, or contain a break, or call another method. | 265
This parameter (symbolizer) of this function is not used. | 277
This parameter (symbolizer) of this function is not used. | 277

### ScaleLine.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
Too many field detected (5 maximum, but 9 actually). Classes that have too many fields could be redesigned to have fewer fields, possibly through some nested object grouping of some of the information. For example, a class with city/state/zipcode fields could instead have one Address field. | 18
Too many field detected (5 maximum, but 9 actually). Classes that have too many fields could be redesigned to have fewer fields, possibly through some nested object grouping of some of the information. For example, a class with city/state/zipcode fields could instead have one Address field. | 18
Using digits at the end of a symbol does not help understanging the meaning of it | 112
Using digits at the end of a symbol does not help understanging the meaning of it | 112
This variable (barLen) seems to be incorrectly named. Let your creativity flow | 118
This variable (barLen) seems to be incorrectly named. Let your creativity flow | 118
This function is far too long (20 maximum, but 39 actually). Violations of this rule usually indicate that the method has too much responsibility. Try to reduce the method size by creating helper methods and removing any copy/pasted code. | 134
This function is far too long (20 maximum, but 39 actually). Violations of this rule usually indicate that the method has too much responsibility. Try to reduce the method size by creating helper methods and removing any copy/pasted code. | 134
Flex specific - You must add child only inside the createChildren method | 214
Flex specific - You must add child only inside the createChildren method | 214
Flex specific - You must add child only inside the createChildren method | 215
Flex specific - You must add child only inside the createChildren method | 215

### SecurityEvent.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1

### SelectFeaturesHandler.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 624
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 624
Too long line (200 maximum, but 246 actually). | 684
Too long line (200 maximum, but 246 actually). | 684

### Size.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 8
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 8
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 9
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 9

### SliderHorizontal.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
Embed metadata detected in source code where a stylesheet may be cleaner | 12
Embed metadata detected in source code where a stylesheet may be cleaner | 12

### SliderVertical.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
Embed metadata detected in source code where a stylesheet may be cleaner | 13
Embed metadata detected in source code where a stylesheet may be cleaner | 13

### SolidFill.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1

### State.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
If this field (UNKNOWN) was meant to be a constant, make it constant. Otherwise, if it is used as a global variable, you may want to redesign this class | 8
If this field (UNKNOWN) was meant to be a constant, make it constant. Otherwise, if it is used as a global variable, you may want to redesign this class | 8
If this field (INSERT) was meant to be a constant, make it constant. Otherwise, if it is used as a global variable, you may want to redesign this class | 9
If this field (INSERT) was meant to be a constant, make it constant. Otherwise, if it is used as a global variable, you may want to redesign this class | 9
If this field (UPDATE) was meant to be a constant, make it constant. Otherwise, if it is used as a global variable, you may want to redesign this class | 10
If this field (UPDATE) was meant to be a constant, make it constant. Otherwise, if it is used as a global variable, you may want to redesign this class | 10
If this field (DELETE) was meant to be a constant, make it constant. Otherwise, if it is used as a global variable, you may want to redesign this class | 11
If this field (DELETE) was meant to be a constant, make it constant. Otherwise, if it is used as a global variable, you may want to redesign this class | 11
If this field (EDIT) was meant to be a constant, make it constant. Otherwise, if it is used as a global variable, you may want to redesign this class | 13
If this field (EDIT) was meant to be a constant, make it constant. Otherwise, if it is used as a global variable, you may want to redesign this class | 13

### StringUtils.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 73
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 73
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 252
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 252
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 314
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 314

### Stroke.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
Long parameter list detected (4 maximum, but 5 actually). Long parameter lists can indicate that a new object should be created to wrap the numerous parameters. Basically, try to group the parameters together. | 36
Long parameter list detected (4 maximum, but 5 actually). Long parameter lists can indicate that a new object should be created to wrap the numerous parameters. Basically, try to group the parameters together. | 36

### Style.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
Too many field detected (5 maximum, but 17 actually). Classes that have too many fields could be redesigned to have fewer fields, possibly through some nested object grouping of some of the information. For example, a class with city/state/zipcode fields could instead have one Address field. | 13
Too many field detected (5 maximum, but 17 actually). Classes that have too many fields could be redesigned to have fewer fields, possibly through some nested object grouping of some of the information. For example, a class with city/state/zipcode fields could instead have one Address field. | 13
ArrayElementType metadata is not specified for this array-type field (_rules). | 20
ArrayElementType metadata is not specified for this array-type field (_rules). | 20
Using digits at the end of a symbol does not help understanging the meaning of it | 125
Using digits at the end of a symbol does not help understanging the meaning of it | 125
Using digits at the end of a symbol does not help understanging the meaning of it | 129
Using digits at the end of a symbol does not help understanging the meaning of it | 129
Using digits at the end of a symbol does not help understanging the meaning of it | 133
Using digits at the end of a symbol does not help understanging the meaning of it | 133
Using digits at the end of a symbol does not help understanging the meaning of it | 137
Using digits at the end of a symbol does not help understanging the meaning of it | 137
Using digits at the end of a symbol does not help understanging the meaning of it | 138
Using digits at the end of a symbol does not help understanging the meaning of it | 138

### Symbolizer.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
This parameter (graphics) of this function is not used. | 30
This parameter (graphics) of this function is not used. | 30

### TMS.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
This private attribute (_serviceVersion) does not seem to be used. | 21
This private attribute (_serviceVersion) does not seem to be used. | 21
ArrayElementType metadata is not specified for this array-type field (_serverResolutions). | 29
ArrayElementType metadata is not specified for this array-type field (_serverResolutions). | 29
Long parameter list detected (4 maximum, but 6 actually). Long parameter lists can indicate that a new object should be created to wrap the numerous parameters. Basically, try to group the parameters together. | 31
Long parameter list detected (4 maximum, but 6 actually). Long parameter lists can indicate that a new object should be created to wrap the numerous parameters. Basically, try to group the parameters together. | 31
This variable (x) is not used. | 41
This variable (x) is not used. | 41
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 41
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 41
This variable (y) is not used. | 42
This variable (y) is not used. | 42
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 42
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 42
This variable (z) is not used. | 43
This variable (z) is not used. | 43

### Tile.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
Too many field detected (5 maximum, but 9 actually). Classes that have too many fields could be redesigned to have fewer fields, possibly through some nested object grouping of some of the information. For example, a class with city/state/zipcode fields could instead have one Address field. | 18
Too many field detected (5 maximum, but 9 actually). Classes that have too many fields could be redesigned to have fewer fields, possibly through some nested object grouping of some of the information. For example, a class with city/state/zipcode fields could instead have one Address field. | 18
Long parameter list detected (4 maximum, but 5 actually). Long parameter lists can indicate that a new object should be created to wrap the numerous parameters. Basically, try to group the parameters together. | 31
Long parameter list detected (4 maximum, but 5 actually). Long parameter lists can indicate that a new object should be created to wrap the numerous parameters. Basically, try to group the parameters together. | 31
This test contains a hard coded boolean value. You could remove it by having 'condition' | 208
This test contains a hard coded boolean value. You could remove it by having 'condition' | 208
This test contains a hard coded boolean value. You could remove it by having 'condition' | 214
This test contains a hard coded boolean value. You could remove it by having 'condition' | 214

### TileEvent.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1

### Trace.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
Too many public fields or functions detected (10 maximum, but 11 actually). A large number of public methods and attributes declared in a class can indicate the class may need to be broken up as increased effort will be required to thoroughly test it. | 26
Too many public fields or functions detected (10 maximum, but 11 actually). A large number of public methods and attributes declared in a class can indicate the class may need to be broken up as increased effort will be required to thoroughly test it. | 26
If this field (map) was meant to be a constant, make it constant. Otherwise, if it is used as a global variable, you may want to redesign this class | 28
If this field (map) was meant to be a constant, make it constant. Otherwise, if it is used as a global variable, you may want to redesign this class | 28
If this field (useFireBugConsole) was meant to be a constant, make it constant. Otherwise, if it is used as a global variable, you may want to redesign this class | 29
If this field (useFireBugConsole) was meant to be a constant, make it constant. Otherwise, if it is used as a global variable, you may want to redesign this class | 29

### TraceEvent.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1

### Unit.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
Too many field detected (5 maximum, but 7 actually). Classes that have too many fields could be redesigned to have fewer fields, possibly through some nested object grouping of some of the information. For example, a class with city/state/zipcode fields could instead have one Address field. | 10
Too many field detected (5 maximum, but 7 actually). Classes that have too many fields could be redesigned to have fewer fields, possibly through some nested object grouping of some of the information. For example, a class with city/state/zipcode fields could instead have one Address field. | 10
If this field (DEGREE) was meant to be a constant, make it constant. Otherwise, if it is used as a global variable, you may want to redesign this class | 12
If this field (DEGREE) was meant to be a constant, make it constant. Otherwise, if it is used as a global variable, you may want to redesign this class | 12
If this field (METER) was meant to be a constant, make it constant. Otherwise, if it is used as a global variable, you may want to redesign this class | 13
If this field (METER) was meant to be a constant, make it constant. Otherwise, if it is used as a global variable, you may want to redesign this class | 13
If this field (KILOMETER) was meant to be a constant, make it constant. Otherwise, if it is used as a global variable, you may want to redesign this class | 14
If this field (KILOMETER) was meant to be a constant, make it constant. Otherwise, if it is used as a global variable, you may want to redesign this class | 14
If this field (FOOT) was meant to be a constant, make it constant. Otherwise, if it is used as a global variable, you may want to redesign this class | 15
If this field (FOOT) was meant to be a constant, make it constant. Otherwise, if it is used as a global variable, you may want to redesign this class | 15
If this field (MILE) was meant to be a constant, make it constant. Otherwise, if it is used as a global variable, you may want to redesign this class | 16
If this field (MILE) was meant to be a constant, make it constant. Otherwise, if it is used as a global variable, you may want to redesign this class | 16
If this field (INCH) was meant to be a constant, make it constant. Otherwise, if it is used as a global variable, you may want to redesign this class | 17
If this field (INCH) was meant to be a constant, make it constant. Otherwise, if it is used as a global variable, you may want to redesign this class | 17
If this field (DOTS_PER_INCH) was meant to be a constant, make it constant. Otherwise, if it is used as a global variable, you may want to redesign this class | 19
If this field (DOTS_PER_INCH) was meant to be a constant, make it constant. Otherwise, if it is used as a global variable, you may want to redesign this class | 19

### Util.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
Imports from the same package are not necessary. | 8
Imports from the same package are not necessary. | 8
Too many methods detected (10 maximum, but 12 actually). A class with too many methods is probably a good suspect for refactoring, in order to reduce its complexity and find a way to have more fine grained objects. | 10
Too many methods detected (10 maximum, but 12 actually). A class with too many methods is probably a good suspect for refactoring, in order to reduce its complexity and find a way to have more fine grained objects. | 10
Too many public fields or functions detected (10 maximum, but 12 actually). A large number of public methods and attributes declared in a class can indicate the class may need to be broken up as increased effort will be required to thoroughly test it. | 10
Too many public fields or functions detected (10 maximum, but 12 actually). A large number of public methods and attributes declared in a class can indicate the class may need to be broken up as increased effort will be required to thoroughly test it. | 10
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 26
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 26
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 26
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 26
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 26
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 26
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 41
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 41
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 58
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 58
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 85
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 85
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 85
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 85
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 86
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 86
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 100
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 100
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 104
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 104
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 106
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 106
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 133
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 133
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 140
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 140
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 152
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 152
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 154
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 154
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 161
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 161
This function is far too long (20 maximum, but 21 actually). Violations of this rule usually indicate that the method has too much responsibility. Try to reduce the method size by creating helper methods and removing any copy/pasted code. | 184
This function is far too long (20 maximum, but 21 actually). Violations of this rule usually indicate that the method has too much responsibility. Try to reduce the method size by creating helper methods and removing any copy/pasted code. | 184
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 194
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 194
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 218
This variable name is too short (3 characters minimum, but 1 actually). Detects when a field, local, or parameter has a very short name. | 218
This variable (s) is not used. | 264
This variable (s) is not used. | 264

### WFS.as

Violation | Line
--- | ---
A high number of imports can indicate a high degree of coupling within an object. (15 maximum but 17 actually). A high number of imports can indicate a high degree of coupling within an object. Rule counts the number of unique imports and reports a violation if the count is above the user defined threshold. | -1
A high number of imports can indicate a high degree of coupling within an object. (15 maximum but 17 actually). A high number of imports can indicate a high degree of coupling within an object. Rule counts the number of unique imports and reports a violation if the count is above the user defined threshold. | -1
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
Too many field detected (5 maximum, but 11 actually). Classes that have too many fields could be redesigned to have fewer fields, possibly through some nested object grouping of some of the information. For example, a class with city/state/zipcode fields could instead have one Address field. | 25
Too many field detected (5 maximum, but 11 actually). Classes that have too many fields could be redesigned to have fewer fields, possibly through some nested object grouping of some of the information. For example, a class with city/state/zipcode fields could instead have one Address field. | 25
Constructor must be as lightweight as possible. No control statement allowed, whereas a cyclomatic complexe of 2 has been detected. The Just-In-Time compiler does not compile constructors. Make them as lightweight as possible, or move the complexity of the code to a method called by the constructor. Then the complexity will be compiled by the JIT. | 74
Constructor must be as lightweight as possible. No control statement allowed, whereas a cyclomatic complexe of 2 has been detected. The Just-In-Time compiler does not compile constructors. Make them as lightweight as possible, or move the complexity of the code to a method called by the constructor. Then the complexity will be compiled by the JIT. | 74
Long parameter list detected (4 maximum, but 9 actually). Long parameter lists can indicate that a new object should be created to wrap the numerous parameters. Basically, try to group the parameters together. | 74
Long parameter list detected (4 maximum, but 9 actually). Long parameter lists can indicate that a new object should be created to wrap the numerous parameters. Basically, try to group the parameters together. | 74
This test contains a hard coded boolean value. You could remove it by having 'condition' | 96
This test contains a hard coded boolean value. You could remove it by having 'condition' | 96
This variable (center) is not used. | 113
This variable (center) is not used. | 113
Nested if statements are not a good design | 132
Nested if statements are not a good design | 132
Nested if statements are not a good design | 132
Nested if statements are not a good design | 132

### WFS100.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
This private method (WFS100) does not seem to be used. | 17
This private method (WFS100) does not seem to be used. | 17
Using digits at the end of a symbol does not help understanging the meaning of it | 17
Using digits at the end of a symbol does not help understanging the meaning of it | 17
This function is far too long (20 maximum, but 25 actually). Violations of this rule usually indicate that the method has too much responsibility. Try to reduce the method size by creating helper methods and removing any copy/pasted code. | 38
This function is far too long (20 maximum, but 25 actually). Violations of this rule usually indicate that the method has too much responsibility. Try to reduce the method size by creating helper methods and removing any copy/pasted code. | 38
Instanciating a variable in a loop can be expensive. | 68
Instanciating a variable in a loop can be expensive. | 68
Instanciating a variable in a loop can be expensive. | 74
Instanciating a variable in a loop can be expensive. | 74
Instanciating a variable in a loop can be expensive. | 88
Instanciating a variable in a loop can be expensive. | 88

### WFS110.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
This private method (WFS110) does not seem to be used. | 17
This private method (WFS110) does not seem to be used. | 17
Using digits at the end of a symbol does not help understanging the meaning of it | 17
Using digits at the end of a symbol does not help understanging the meaning of it | 17
This function is far too long (20 maximum, but 29 actually). Violations of this rule usually indicate that the method has too much responsibility. Try to reduce the method size by creating helper methods and removing any copy/pasted code. | 38
This function is far too long (20 maximum, but 29 actually). Violations of this rule usually indicate that the method has too much responsibility. Try to reduce the method size by creating helper methods and removing any copy/pasted code. | 38
Instanciating a variable in a loop can be expensive. | 80
Instanciating a variable in a loop can be expensive. | 80
Instanciating a variable in a loop can be expensive. | 94
Instanciating a variable in a loop can be expensive. | 94

### WFSFormat.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
Constructor must be as lightweight as possible. No control statement allowed, whereas a cyclomatic complexe of 4 has been detected. The Just-In-Time compiler does not compile constructors. Make them as lightweight as possible, or move the complexity of the code to a method called by the constructor. Then the complexity will be compiled by the JIT. | 25
Constructor must be as lightweight as possible. No control statement allowed, whereas a cyclomatic complexe of 4 has been detected. The Just-In-Time compiler does not compile constructors. Make them as lightweight as possible, or move the complexity of the code to a method called by the constructor. Then the complexity will be compiled by the JIT. | 25
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 45
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 45
Too long line (200 maximum, but 421 actually). | 46
Too long line (200 maximum, but 421 actually). | 46
Too long line (200 maximum, but 214 actually). | 70
Too long line (200 maximum, but 214 actually). | 70
Too long line (200 maximum, but 215 actually). | 72
Too long line (200 maximum, but 215 actually). | 72

### WFSParams.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1

### WKTFormat.as

Violation | Line
--- | ---
A high number of imports can indicate a high degree of coupling within an object. (15 maximum but 18 actually). A high number of imports can indicate a high degree of coupling within an object. Rule counts the number of unique imports and reports a violation if the count is above the user defined threshold. | -1
A high number of imports can indicate a high degree of coupling within an object. (15 maximum but 18 actually). A high number of imports can indicate a high degree of coupling within an object. Rule counts the number of unique imports and reports a violation if the count is above the user defined threshold. | -1
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 29
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 29
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 56
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 56
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 57
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 57
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 76
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 76
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 77
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 77
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 108
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 108
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 159
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 159

### WMS.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
Long parameter list detected (4 maximum, but 7 actually). Long parameter lists can indicate that a new object should be created to wrap the numerous parameters. Basically, try to group the parameters together. | 23
Long parameter list detected (4 maximum, but 7 actually). Long parameter lists can indicate that a new object should be created to wrap the numerous parameters. Basically, try to group the parameters together. | 23
This test contains a hard coded boolean value. You could remove it by having 'condition' | 41
This test contains a hard coded boolean value. You could remove it by having 'condition' | 41
This test contains a hard coded boolean value. You could remove it by having 'condition' | 53
This test contains a hard coded boolean value. You could remove it by having 'condition' | 53
This test contains a hard coded boolean value. You could remove it by having '!condition' | 61
This test contains a hard coded boolean value. You could remove it by having '!condition' | 61

### WMSC.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
Long parameter list detected (4 maximum, but 7 actually). Long parameter lists can indicate that a new object should be created to wrap the numerous parameters. Basically, try to group the parameters together. | 14
Long parameter list detected (4 maximum, but 7 actually). Long parameter lists can indicate that a new object should be created to wrap the numerous parameters. Basically, try to group the parameters together. | 14

### WMSGetFeatureInfo.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
Too many field detected (5 maximum, but 7 actually). Classes that have too many fields could be redesigned to have fewer fields, possibly through some nested object grouping of some of the information. For example, a class with city/state/zipcode fields could instead have one Address field. | 20
Too many field detected (5 maximum, but 7 actually). Classes that have too many fields could be redesigned to have fewer fields, possibly through some nested object grouping of some of the information. For example, a class with city/state/zipcode fields could instead have one Address field. | 20
This method is too complex. Maximum complexity is 10, but its cyclomatic complexity was 12 | 84
This method is too complex. Maximum complexity is 10, but its cyclomatic complexity was 12 | 84
This function is far too long (20 maximum, but 22 actually). Violations of this rule usually indicate that the method has too much responsibility. Try to reduce the method size by creating helper methods and removing any copy/pasted code. | 84
This function is far too long (20 maximum, but 22 actually). Violations of this rule usually indicate that the method has too much responsibility. Try to reduce the method size by creating helper methods and removing any copy/pasted code. | 84

### WMSGetFeatureInfoParams.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
Too many field detected (5 maximum, but 11 actually). Classes that have too many fields could be redesigned to have fewer fields, possibly through some nested object grouping of some of the information. For example, a class with city/state/zipcode fields could instead have one Address field. | 10
Too many field detected (5 maximum, but 11 actually). Classes that have too many fields could be redesigned to have fewer fields, possibly through some nested object grouping of some of the information. For example, a class with city/state/zipcode fields could instead have one Address field. | 10
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 21
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 21
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 22
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 22

### WMSParams.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
Too many field detected (5 maximum, but 9 actually). Classes that have too many fields could be redesigned to have fewer fields, possibly through some nested object grouping of some of the information. For example, a class with city/state/zipcode fields could instead have one Address field. | 10
Too many field detected (5 maximum, but 9 actually). Classes that have too many fields could be redesigned to have fewer fields, possibly through some nested object grouping of some of the information. For example, a class with city/state/zipcode fields could instead have one Address field. | 10
Long parameter list detected (4 maximum, but 6 actually). Long parameter lists can indicate that a new object should be created to wrap the numerous parameters. Basically, try to group the parameters together. | 23
Long parameter list detected (4 maximum, but 6 actually). Long parameter lists can indicate that a new object should be created to wrap the numerous parameters. Basically, try to group the parameters together. | 23

### WellKnownMarker.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
Long parameter list detected (4 maximum, but 6 actually). Long parameter lists can indicate that a new object should be created to wrap the numerous parameters. Basically, try to group the parameters together. | 29
Long parameter list detected (4 maximum, but 6 actually). Long parameter lists can indicate that a new object should be created to wrap the numerous parameters. Basically, try to group the parameters together. | 29
Long switch case detected (3 lines maximum, but 5 actually). A switch case statement should be either empty, or contain a break, or call another method. | 64
Long switch case detected (3 lines maximum, but 5 actually). A switch case statement should be either empty, or contain a break, or call another method. | 64

### WheelHandler.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1

### XMLRequest.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 26
Do not use Object class. It is a bad practice to use the dynamic class Object. Prefer using strongly typed object, or marker interface in order to avoid silent compilation errors while refactoring | 26
Constructor must be as lightweight as possible. No control statement allowed, whereas a cyclomatic complexe of 9 has been detected. The Just-In-Time compiler does not compile constructors. Make them as lightweight as possible, or move the complexity of the code to a method called by the constructor. Then the complexity will be compiled by the JIT. | 26
Constructor must be as lightweight as possible. No control statement allowed, whereas a cyclomatic complexe of 9 has been detected. The Just-In-Time compiler does not compile constructors. Make them as lightweight as possible, or move the complexity of the code to a method called by the constructor. Then the complexity will be compiled by the JIT. | 26
Long parameter list detected (4 maximum, but 7 actually). Long parameter lists can indicate that a new object should be created to wrap the numerous parameters. Basically, try to group the parameters together. | 26
Long parameter list detected (4 maximum, but 7 actually). Long parameter lists can indicate that a new object should be created to wrap the numerous parameters. Basically, try to group the parameters together. | 26
Too long line (200 maximum, but 200 actually). | 26
Too long line (200 maximum, but 200 actually). | 26
This catch statement is empty | 75
This catch statement is empty | 75
This statement is empty. | 77
This statement is empty. | 77

### ZoomBoxEvent.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1

### ZoomBoxHandler.as

Violation | Line
--- | ---
The copyright header is missing in this file | -1
The copyright header is missing in this file | -1
A constructor should not have a return type. Even if this is syntactically correct, there should not be a return type for a constructor. | 28
A constructor should not have a return type. Even if this is syntactically correct, there should not be a return type for a constructor. | 28
Flex specific - You must add child only inside the createChildren method | 49
Flex specific - You must add child only inside the createChildren method | 49
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 84
This variable name is too short (3 characters minimum, but 2 actually). Detects when a field, local, or parameter has a very short name. | 84