The following document contains the listing of user tags found in the code. Below is the summary of the occurrences per tag.
| Tag Class | Total number of occurrences | Tag strings used by tag class |
|---|---|---|
| @todo | 0 | @todo |
| TODO | 10 | TODO |
Each tag is detailed below:
Number of occurrences found in the code: 10
| org.bitrepository.integrityclient.IntegrityServiceComponentFactory | Line |
|---|---|
| implement the database based integrity cache. | 122 |
| org.bitrepository.integrityclient.cache.MemoryBasedIntegrityCache | Line |
| move to test? | 46 |
| org.bitrepository.integrityclient.checking.SimpleIntegrityChecker | Line |
| validate the checksum type (e.g. algorithm and salt). | 134 |
| also validate, that all pillars contains the files. | 135 |
| org.bitrepository.integrityclient.collector.eventhandler.IntegrityAlarmDispatcher | Line |
| ??? | 111 |
| missing types: RiskAreaType.UNKNOWN, RiskImpactScoreType.UNKNOWN, RiskProbabilityScoreType.UNKNOWN | 116 |
| org.bitrepository.integrityclient.collector.eventhandler.IntegrityStorageChecksumsUpdater | Line |
| handle differently if special case (e.g. PillarFailure). | 85 |
| org.bitrepository.integrityclient.collector.eventhandler.IntegrityStorageFileIDsUpdater | Line |
| handle differently if special case (e.g. PillarFailure). | 84 |
| org.bitrepository.integrityclient.scheduler.TimerIntegrityInformationScheduler | Line |
| Should the interval rather be a suggestion from the trigger? | 74 |
| Should triggers be defined in configuration? How? | 75 |
