Issue #2038 Correct unregisterFromBandwidthEventBus() to actually do it

Change-Id: Ic82c974dcf354d9fb871b1b2f81cea52e2502fe8

Former-commit-id: 2cfe1506a4 [formerly 0393cec5d5] [formerly 2cfe1506a4 [formerly 0393cec5d5] [formerly 9f6bd8b32b [formerly 198c9895608d22b3e3a616f2812628be32da514b]]]
Former-commit-id: 9f6bd8b32b
Former-commit-id: 617fdd6b44 [formerly 3cb8e1336c]
Former-commit-id: b9f992626c
This commit is contained in:
Dustin Johnson 2013-07-09 14:55:11 -05:00
parent 364a7ec1b6
commit 06ce541b67

View file

@ -116,6 +116,7 @@ import com.raytheon.uf.edex.datadelivery.bandwidth.util.BandwidthUtil;
* May 20, 2013 1650 djohnson Add in capability to find required dataset size.
* Jun 03, 2013 2038 djohnson Add base functionality to handle point data type subscriptions.
* Jun 20, 2013 1802 djohnson Check several times for the metadata for now.
* Jul 09, 2013 2038 djohnson Correct unregisterFromBandwidthEventBus() to actually do it.
* </pre>
*
* @author dhladky
@ -1692,7 +1693,7 @@ public abstract class BandwidthManager extends
* Unregister from the {@link BandwidthEventBus}.
*/
private void unregisterFromBandwidthEventBus() {
BandwidthEventBus.register(this);
BandwidthEventBus.unregister(this);
}
/**