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 | 18 | TODO |
Each tag is detailed below:
Number of occurrences found in the code: 18
| org.bitrepository.client.AbstractClient | Line |
|---|---|
| Kill any lingering timer threads | 96 |
| org.bitrepository.client.conversation.GeneralConversationState | Line |
| How should this be handled? | 77 |
| org.bitrepository.client.conversation.mediator.ConversationMediatorTest | Line |
| Auto-generated method stub | 90 |
| org.bitrepository.common.utils.FileUtils | Line |
| verify, that it has successfully been removed. | 119 |
| org.bitrepository.common.utils.StreamUtils | Line |
| move to a utility class. | 43 |
| org.bitrepository.protocol.FileExchange | Line |
| Interface is extremely HTTP-centric. Should be generified. HTTP-centricity shines through to usage. | 39 |
| org.bitrepository.protocol.ProtocolComponentFactory | Line |
| handle different? | 77 |
| org.bitrepository.protocol.activemq.ActiveMQMessageBus | Line |
| add retries for whenever a JMS exception is thrown. Currently it is very unstable to connection issues. | 101 |
| currently creates only topics. | 104 |
| Switch to use a session pool/producer poll to allow multithreaded message sending, see https://sbforge.org/jira/browse/BITMAG-357. | 124 |
| org.bitrepository.protocol.fileexchange.HttpsServerConnector | Line |
| handle. | 107 |
| handle different? We currently accept everybody. | 113 |
| org.bitrepository.protocol.http.HTTPFileExchange | Line |
| read the configurations for the server where the data should be uploaded from settings. | 46 |
| perhaps make it synchronized around the URL, to prevent data from trying to uploaded several times to the same location simultaneously. | 183 |
| org.bitrepository.protocol.messagebus.MessageBus | Line |
| define a function for reconnecting to the message bus. Part of the issue BITMAG-166 | 35 |
| org.bitrepository.protocol.performancetest.MessageBusNumberOfListenersStressTest | Line |
| Important note for testers: The number of listeners should be regulated through the 'NUMBER_OF_LISTENERS' constant. When using many listeners, the DEFAULT_WAIT_TIME should be increased, e.g. 5000 for 25 listeners and 15000 for 100 listeners. Otherwise it is not ensured, that all the messagelisteners will receive all the messages before the validation. | 50 |
| org.bitrepository.service.audit.AuditTrailContributerDAO | Line |
| improve performance (only reconnect every-so-often)... | 72 |
| BITMAG-646 | 103 |
