Tag List Report

The following document contains the listing of user tags found in the code. Below is the summary of the occurrences per tag.

Tag ClassTotal number of occurrencesTag strings used by tag class
@todo0@todo
TODO18TODO

Each tag is detailed below:

TODO

Number of occurrences found in the code: 18

org.bitrepository.protocol.FileExchangeLine
Interface is extremely HTTP-centric. Should be generified. HTTP-centricity shines through to usage.39
org.bitrepository.protocol.ProtocolComponentFactoryLine
handle different?91
org.bitrepository.protocol.activemq.ActiveMQMessageBusLine
add retries for whenever a JMS exception is thrown. Currently it is very unstable to connection issues.92
currently creates only topics.95
Switch to use a session pool/producer poll to allow multithreaded message sending, see https://sbforge.org/jira/browse/BITMAG-357.115
According to javadoc, topics should be looked up in another fashion. See http://download.oracle.com/javaee/6/api/javax/jms/Session.html#createTopic(java.lang.String)529
org.bitrepository.protocol.fileexchange.HttpsServerConnectorLine
handle.107
handle different? We currently accept everybody.113
org.bitrepository.protocol.http.HTTPFileExchangeLine
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.http.HTTPSFileExchangeLine
replace with configurable values.61
should these be constants?71
handle.130
handle different? We currently accept everybody.193
org.bitrepository.protocol.http.HTTPSTestLine
--No comment--124
org.bitrepository.protocol.mediator.ConversationMediatorTestLine
Auto-generated method stub121
org.bitrepository.protocol.messagebus.MessageBusLine
define a function for reconnecting to the message bus. Part of the issue BITMAG-16635
org.bitrepository.protocol.performancetest.MessageBusNumberOfListenersStressTestLine
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.48